Informatica Intelligent Data Management Cloud (IDMC) Reviews

We use the tool to implement customer, product, and entity masters. We also use TDM to generate synthetic data, but not in real-time scenarios.

It's a multi-domain master data management system. The solution is easier to use compared to the other solutions. The security is good. The governance model is good. All the elements that I expect are available in the product.

The user interface can be a bit more functionality-aligned.

I have been using the solution for the last 15 years.

I rate the stability a nine out of ten.

The product is scalable.

The support team does not provide much support.

The initial setup was okay. I rate the ease of setup a five out of ten. The tool can be deployed in a minimum of eight to ten months. The implementation requires at least a team of five members. Maintenance depends on the customer's requirements. If the customer's requirements keep changing, we need a team to maintain the tool. Otherwise, one or two Informatica developers are sufficient to maintain the product.

The price is comparable.

All the tools have similar capabilities. There is nothing superior in Informatica. I'm a software integrator. I work for an IT company. I'm not the consumer. I will recommend the product to others, but it depends on the customers’ needs.

If an organization needs a good customer master, product master, or partner master, Informatica MDM will be a good choice. The solution has been in the industry for quite a long time. It has all the elements I look for in a master data management system except for customer support. All other things are fine.

Overall, I rate the solution a seven and a half out of ten.

Data quality is missing enterprise-wide in our bank. We use the solution for all the customer data to judge the metrics of software data quality from the source systems.

Server maintenance, server hosting, backup, restoration, and DB capabilities are not needed in the cloud. There is no crashing of the servers. The admin part is very seamless in the cloud, while administration is a big task for the on-premises version.

The on-premises version is very mature, but many of the on-premises features are missing in the cloud. It is still in the development stage and has not yet matured in the cloud. The tool has a lot of product errors that need to be fixed. We face a lot of internal product errors while doing the configuration and quality checks.

The on-premises version has many use case transformations, but they are missing in the cloud. The cloud version has only four to five types of use case transformations. You cannot import the data discovery rules you create in the solution to the Cloud Data Governance and Catalog (CDGC).

I have been using Informatica Cloud Data Quality for six months.

We face many glitches during the configuration because it is a new product. It will take another year to mature.

The solution's scalability is seamless in the cloud. You can scale the solution within one or two hours.

The solution's customer support is wonderful, but they are not up to the mark knowledge-wise.

Positive

The solution can be implemented in one or two days. There are steps available to deploy the tool. One person is enough to procure the VM or the server.

Informatica Cloud Data Quality is a costly solution.

The solution's competitors include Oracle Data Quality, Collibra, and Azure Purview.

The solution provides data standardization capabilities. Since Informatica Cloud Data Quality is a SaaS solution, it does not require any maintenance. Since it is a cloud product, many connectors have configuration issues. They have to add some other parameters in the tool levels. We face such challenges in the cloud, not on-premises.

Overall, I rate the solution an eight out of ten.

We use Informatica Cloud Data Integration to load data from files to TelSource or Oracle tables. We also apply business rules to transform the data before loading it into the respective targets.

Most of the features are good. The advanced features like task flow and conditional integration are particularly useful. There are multiple transformations we can use in Dashflow, which are beneficial. We don't use features like centralization and data marketing because they aren't relevant to our use case. Our primary focus is on task flow, which allows us to design our jobs and execute them conditionally.

Some features require an additional license, such as Elastic Mappings. Most of the features provided are through Elastic Mappings, not the data integration service which causes restrictions. For example, the recently enabled source partitioning isn't applicable to Salesforce, which we use as our target or source. We primarily seek features that enhance performance for Salesforce and ICS Integration, aiming to reduce job execution time.

We don't have the license for Elastic Mapping, so we can't use that feature. Most of the new features added by Informatica are through Elastic Mapping. It would be helpful to have features like multithreading or partitioning for Salesforce to enhance performance.

I have been using Informatica Cloud Data Integration for five years.

The product is stable.

I rate the solution’s stability a seven out of ten.

20-30 users are using this solution.

I rate the solution’s scalability a five out of ten.

Support is good.

Positive

The initial setup is very easy. When I first started using it, I installed a 30-day trial version. I personally explored it during that period, and it was good.

It takes 30-40 minutes depending on the jobs.

I rate the initial setup a ten out of ten, where one is difficult, and ten is easy.

The team is very user-friendly, meeting our expectations much like PowerPoint does.

It supports integration with most cloud sources, including AWS, and has various cloud connectors. So, It's a good choice for anyone.

Overall, I rate the solution a seven out of ten.

Informatica Axon is typically used for data governance, where we establish policies and business glossaries.

Users can benefit from Axon's business lineage. Axon has something called Overlay, which can be used to extend the technical lineage. You can also extend it to stakeholders, all the compliance policies, and all the overlaying business rules. All of these can be seen in the same lineage.

I want to get a deeper understanding of the logic that is being used in the ETL. Informatica Axon does not provide complete transparency about the level of detailing you need and the logic used in ETL. I cannot use Google Fusion for ETL because I don't have a connector within Informatica Axon. I am stuck if I don't have a connector with an ETL tool.

One of the biggest disadvantages of Informatica is that it's very expensive. Many clients don't want to go with Informatica Axon because of its cost structure. You have to buy every component separately. If a customer wants governance, they obviously would need cataloging and lineage also.

Other tools like Collibra have cataloging, lineage, and governance in the same package. You don't need to buy them separately. With Informatica, you have to buy Axon for governance and EDC for cataloging and lineage. So, it becomes difficult for customers to pay for every component.

I have been using Informatica Axon for seven years.

We haven’t faced any stability issues with Informatica Axon.

Scalability is not really a factor in data governance because the volume and storage of metadata is not more than a couple of gigabytes.

The solution provides good technical support.

Positive

The solution's initial setup is easy, but you typically need Informatica support to run some of the preliminary tests. I've heard that the solution will be available on the cloud. Once it is available as software as a service (SaaS), you don't need to install it; you only need to configure it.

Typically, it takes around two days for the solution's installation and integration with the entire Active Directory and EDC. Then, it may take another day for testing. One engineer is enough to do all this work.

Only using Axon will not give you all the benefits, but you will see benefits when Axon, EDC, and IDQ are all plugged in together. It is difficult to get benefits from Axon as a standalone solution.

The solution's pricing model is easy, but it is very expensive.

Informatica Axon has a Marketplace that comes at an additional cost. Other tools like Collibra have built-in collaboration features, and you don't need to buy them separately. Collaboration features like collaborating on data sets, tagging them, and making a request are available in the Informatica Axon Marketplace.

It's not difficult to maintain the tool as long as someone has been trained in administration because Axon has many components. You need to understand how to change the logo of your screen size and how to change the dashboard wizard.

You also need to understand the product's configurations with other tools, personalize your dashboard, customize it, and add roles. There is a learning curve there. You need to train a person to be an administrator, and once they are trained, they can do the role better.

There is an NLP enabled with the solution, but it is not really that great. There is still room for growth in Informatica Axon's AI space.

Although expensive, Informatica Axon is very easy to learn, and you don't need to customize it much. Once you have the tool, you start uploading things. The solution is very easy to use because it has proper documentation and user guides.

If you want to set up business rules, Informatica Axon will give you a readymade template and ask you to start filling it out. You will be told about the mandatory and non-mandatory fields, and as long as you understand what the fields are required for, it's very easy to start filling out. Someone new to governance can get the hang of it and easily start filling in the details. You can have Axon implemented very quickly.

I am more involved with governance, cataloging lineage, EDC, and IDQ. I am getting a little bit into master data management and data security.

Overall, I rate the solution an eight out of ten.

So my use case was on migration.  I've been using these products for migration activities. And providing any QA solution for the integration to other platforms like Databricks.

There are newer technologies in the market that offer better solutions compared to traditional ETL operations. For example, if we use Spark on Databricks, it's more optimized and runs much faster due to its backend capabilities. Whereas Informatica Inc.'s Cloud Services provide cloud-based solutions. The ETL works on the Informatica engine, which is comparatively slow. But the compatibility of data and other integration and data warehouse works well for IICS.

The interface is really good. Another valuable feature is that it is user-friendly.

There are a few improvements which can be done. So those are on data governance and making an image of each object that is being created on top of Informatica, I mean, on top of applications. So those need areas to be improved.

The logging methods are really traditional. So logging, in order to track any operations happening on this interface, will catch a log file. That needs to be more precise.

In future releases as well, I would like to see additional features. So there is no platform where code conversion can happen easily. For example, if you want to move Informatica jobs in various areas, it's quite easy and straightforward. But still, you require some manual intervention for code changes that need to be done throughout the platform. So these things need to be improved. 

And other things are the compatibility of other services. For example, if you have a running Spark code and you want to run the Spark code into Informatica IICS, which is not compatible, so you need to rewrite the whole syntax to make it compatible. So those are the areas that really need improvement.

I have been using Informatica for three years. We currently use the version Informatica Cloud IICS.

Stability is good. I would rate it a seven out of ten. 

Scalability is good since from on-prem to cloud, there's a huge performance boost. So on a scale from one to ten, I would rate it eight.

The setup is complex. Because it's not about the data; it's about the complexity of the pipeline, the complexity of models which have been designed for data engineering. And it's not something straightforward, and the migration cost goes higher on this aspect for this reason.

We have multiple platforms with it. Some of them are running on-prem, and some of them are running on the cloud.

There is definitely an ROI because many companies are preferring to put data in the cloud, and they want to reduce the migration cost. So without any major efforts or challenges in the migration activities, if that's the case, then moving from Informatica on-prem to IICS is a better choice.

Comparatively, other services are providing a lower price, but since moving from Informatica on-prem to IICS, the pricing factor is much better. So when we compare two platforms of the same vendor, it's a good price.

On the evaluation, I have personally evaluated the migration work that I have done. So it is really easy for Informatica users who have been using the same on-prem product. For them, there won't be any challenges in learning any technical aspects of the cloud. So it is almost straightforward. And there are good services provided by Informatica, like integrated things and driver compatibility. So, everything looks much better when it is in the cloud.

Overall, I would rate the solution an eight out of ten.

Informatica Cloud Data Integration is being used to transform data. Primarily, it is for creating data pipelines.

Informatica Cloud Data Integration is being used to transform data. Primarily, it is for creating data pipelines.

Integration is a valuable feature. Currently, the integration makes our security more robust, especially when compared to IICS, where we would need to make arrangements through native or other ways to handle that, and here using sum up makes our lives easier.

With the solution, we had some issues, and we have every day, and we used to open a ticket. Sometimes, there are data issues and transformation issues. So things are not very mature. They need to improve in the aforementioned areas. We are hoping that it will be sorted out in some time, and we will get to experience a hassle-free life.

My company does business with Informatica. We are using their product. I have been using Informatica Cloud Data Integration for four to five years. I am an end user of the solution. Also, I am using the solution's latest version.

I think they are working. Their engineers are still working on some transformations and some features. It is not as stable as they are thinking, but in the last two years, we have seen good progress. So, we are hoping for a similar thing in the future as well. So it is scalable. But, stability-wise, I think that a more stable version is going to come.

I think it is a scalable product. Around a hundred users are using the solution in my company.

The support is very good. On a scale of one to ten, I rate the technical support between eight and ten.

Positive

So we've got many solutions. Not before going to Informatica, but we were evaluating and working with other sets of tools as well. So, on AWS, it is EMR and Glue. We quite frequently use Glue for data pipelines. We also use SAP S/4HANA for delegation. I like IPC and IICS because I have experience in them for the last fifteen years, and I'm working using the same tools. So, I mean, it is my biased opinion. Otherwise, since I have not caught exposure to the other tools in the market that the people in my company are using in different teams, I don't have much exposure to them. Had I gone through those experiences, I would probably have recommended some other tools as well. Currently, I'm in this industry using this tool only, so I recommend it only for that reason. 

The initial setup was very easy. Currently, we are in a deployment process. We've not yet orchestrated that part, but we are in the process of creating the deployment pipelines.

I have deployed the solution on the cloud. Also, there is no maintenance required for the solution.

Cost-wise, I think it is on the higher side, and that is why we are looking for some better options. Licensing costs are huge compared to other players in the market and for my company.

It's a good tool to start with in the beginning.

The product is maturing and has not matured yet. If I look at the market, there are other tools that are providing this stable solution. I rate the overall solution between five to six out of ten.

We use the solution for ETL.

It's a powerful tool to create data warehouse solutions for our clients. We take unstructured data and use Informatica Cloud to structure it in various ways, making it usable on a reporting front end. This enables clients to make informed business decisions based on the data.

It's the accessibility and the range of features that stand out. Before using Informatica Cloud, we were working with Informatica PowerCenter. The transition from PowerCenter to Cloud wasn't entirely effortless, but it was seamless enough for our developers to adapt and continue their work smoothly.

Our main issue is transitioning from on-premise to cloud data storage. As many clients move their data to cloud platforms like Azure, Snowflake, and AWS, we're encountering problems with Informatica. Errors that were straightforward and clear with on-premise databases now appear ambiguous in cloud environments. Our developers spend significant time reducing these generic errors, often simple issues like a column not accepting null values. This lack of clarity is causing unnecessary delays as they have to sift through logs or contact support to diagnose problems that would have been more easily identified in an on-premise setup.

I have been using Informatica Cloud Data Integration as a financial partner for over five years.

We have about seven developers. It is a scalable solution.

When errors arise, contacting support can be frustrating. Sometimes, the technician can't solve the issue and transfers us to someone else. This makes us less confident that the person helping us is truly equipped to resolve the problem.

Neutral

The initial setup is simple and depends on the task. However, it usually takes a couple of hours if development is complete and we're moving from the development environment to production.

ROI is strong because we have a structured portal that ensures development is done correctly. It is shareable, scalable, and equipped with enough monitoring tools to quickly address any issues. Ultimately, the client doesn't care what tools we use. They just want problems resolved quickly. Informatica provides the necessary tools and features to help us do that effectively.

It has premium pricing. Depending on what we're working on and which features we're using within Informatica, there can be additional costs. It's mostly data integration, but you might need to upgrade your license to include other aspects of Informatica. Certain connectors require a license upgrade to access.

Overall, I rate the solution an eight out of ten.

We use the solution for data cataloging and lineage.

The valuable feature is metadata management. If you want to trace sensitive data, you can auto-classify them. You can search for sensitive information through EDC. Using Discovery, you can identify if there is any type of data set.

EDC is only used for cataloging and meetings. Currently, not many different databases are integrated with it. The ETL logic should be visible within the tool. If EDC is integrated with Axon, you will see the data lineage and catalog because of EDC. If EDC is removed, you cannot see any lineage or catalog.

We need EDC on the application level. Currently, it is only at a system level. It can be shown as an application layer between policies or regulations. This kind of feature can be enabled.

The integration with other data management tools can be enhanced. For instance, there is no integration with tools like Collibra or Hubview.

I have been using Informatica Enterprise Data Catalog for seven years.

The solution is stable.

EDC needs many ports to run. Therefore, to improve performance, you need to increase the number of cores.

The initial setup is easy and takes two weeks to complete. One person is enough to deploy it.

EDC gives you a better understanding of architecture and the system used. You cannot use EDC completely unless you have access.

The product is expensive.

EDC is a standalone application, so it doesn’t really make much sense. It doesn’t give you a lot of features that way; it’s primarily for cataloging and classification. Nobody would buy EDC as a standalone application. When people are buying EDC, it’s always with Axon.

I recommend buying the solution altogether with Axon.

Overall, I rate the solution as seven out of ten.