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.
When we're dealing with huge amounts of data, we need to reach out to Informatica. There are some kinds of API records that we need to modify configurations for. Application integration, as compared to data, is a bit slow, and it can't handle millions of records. There could be a lot more application integration. Like data integration, we find there are a lot of places where we can go ahead and improve performance. When it comes to application integration as a developer, we don't have that much flexibility. We have constraints. Our hands are tied, and we can't do anything. We need to speak with either the target system or the core system and say, "Okay, do this thing."
Senior Manager at Conduent (formerly Xerox Services)
Real User
Top 5
2022-11-30T10:47:07Z
Nov 30, 2022
Recently, we're trying to connect to the Amazon API. There's no direct way to connect to Amazon APIs from Informatica Cloud. From Postman, there's a signature site called AWS Signature, which would actually generate the signatures for us with AWS APIs. In Informatica Cloud, we have to build the logic, and then we can generate the signature and hit the AWS APIs. Instead of generating that signature, it would be better if we could have the same connector in Informatica Cloud. Sometimes when I open the processes or any service connectors, the labels are not properly displayed. The backend names are displayed rather than the front end label. I usually log out and log back in, and sometimes it disappears, and sometimes it doesn't.
Learn what your peers think about Informatica Intelligent Data Management Cloud (IDMC). Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
Informatica Intelligent Data Management Cloud (IDMC) is a robust platform used by banks, financial institutions, and health sector organizations for data management, governance, and compliance.
IDMC provides comprehensive tools for data discovery, profiling, masking, and transformation. It supports Salesforce integration, real-time data streaming, and scalable data management solutions. Health organizations manage national product catalogs while financial entities focus on data protection and...
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.
When we're dealing with huge amounts of data, we need to reach out to Informatica. There are some kinds of API records that we need to modify configurations for. Application integration, as compared to data, is a bit slow, and it can't handle millions of records. There could be a lot more application integration. Like data integration, we find there are a lot of places where we can go ahead and improve performance. When it comes to application integration as a developer, we don't have that much flexibility. We have constraints. Our hands are tied, and we can't do anything. We need to speak with either the target system or the core system and say, "Okay, do this thing."
Recently, we're trying to connect to the Amazon API. There's no direct way to connect to Amazon APIs from Informatica Cloud. From Postman, there's a signature site called AWS Signature, which would actually generate the signatures for us with AWS APIs. In Informatica Cloud, we have to build the logic, and then we can generate the signature and hit the AWS APIs. Instead of generating that signature, it would be better if we could have the same connector in Informatica Cloud. Sometimes when I open the processes or any service connectors, the labels are not properly displayed. The backend names are displayed rather than the front end label. I usually log out and log back in, and sometimes it disappears, and sometimes it doesn't.
I'd like to see a change in Informatica's pricing model. It's a common issue with Informatica in their cloud offerings.