April 28, 2020

Verified User
Employee in Information Technology
Consumer Services Company, 501-1000 employeesLikelihood to Recommend
If your environment is clean and well organized, but at the same time has many application domains with their own data sources, Informatica MDM can be a really good factor in maintaining "single points of truth" for all this data. However, the more application domains you have, the less "clean" your environment becomes. If your application domain landscape consists of multiple technologies (C#, Oracle, JAVA, web-based, windows services, console apps, third-party tools, etc), your environment becomes a real nightmare to maintain unless you implement a service-oriented approach. And this is where Informatica MDM fails completely since it promotes a "point to point" scenario.
At least this is my experience. It could be that Informatica MDM supports a service-oriented approach, but I have not seen this. I could be that the developers in my organization who have expert Informatica MDM knowledge are just more "point to point" oriented. But even if that is the case, it's a valid argument against Informatica MDM, since it's already hard enough to find developers who are dedicated to this product, it becomes impossible to find SOA oriented developers.
At least this is my experience. It could be that Informatica MDM supports a service-oriented approach, but I have not seen this. I could be that the developers in my organization who have expert Informatica MDM knowledge are just more "point to point" oriented. But even if that is the case, it's a valid argument against Informatica MDM, since it's already hard enough to find developers who are dedicated to this product, it becomes impossible to find SOA oriented developers.