Apache Camel is an open source integration platform.
N/A
Informatica MDM
Score 8.2 out of 10
N/A
Informatica MDM is an enterprise master data management solution that competes directly with IBM's InfoSphere and Oracle's Siebel UCM product.Informatica MDM and the company's 360 applications present a multidomain solution with flexibility to support any master data domain and relationship—whether on-premises, in the cloud, or both.
Message brokering across different systems, with transactionality and the ability to have fine tuned control over what happens using Java (or other languages), instead of a heavy, proprietary languages. One situation that it doesn't fit very well (as far as I have experienced) is when your workflow requires significant data mapping. While possible when using Java tooling, some other visual data mapping tools in other integration frameworks are easier to work with.
Informatica MDM is a complete MDM solution, from ingestion to data exposition. This tool helps us in gathering customer data, and also it makes it possible for us to support our customers relationships and build customer-related strategies to improve their experience which helps to drive sales geometry and growth and customers satisfaction. On the other hand of price is relatively competitive.
Camel has an easy learning curve. It is fairly well documented and there are about 5-6 books on Camel.
There is a large user group and blogs devoted to all things Camel and the developers of Camel provide quick answers and have also been very quick to patch Camel, when bugs are reported.
Camel integrates well with well known frameworks like Spring, and other middleware products like Apache Karaf and Servicemix.
There are over 150 components for the Camel framework that help integrate with diverse software platforms.
This program raises us to a professional level where we have better versatility to control all the media of my work and have a correct response for each scenario.
It is essential to be right about the destination and development of my data, Informatica MDM is here to simplify all these processes for its users.
It is unfortunate how this program has a couple of limitations in terms of insertions; it does not have the ability to agglomerate and archive the data in real-time by groups.
To have automation functions, the program is very limited in performing one task at a time, compared to other systems that perform functions simultaneously.
I'm not sure since I never used support. My colleagues never had any issues with it, therefore my rating would be an 8 with a certain range of uncertainty.
If you are looking for a Java-based open source low cost equivalent to webMethods or Azure Logic Apps, Apache Camel is an excellent choice as it is mature and widely deployed, and included in many vendored Java application servers too such as Redhat JBoss EAP. Apache Camel is lacking on the GUI tooling side compared to commercial products such as webMethods or Azure Logic Apps.
Informatica MDM has proven it's worth in the organization by driving the revenue growth. It saves our lot of time by filtering out duplicate values and helps in solving critical business problems. It is very helpful when we deal with a lot of data. Apart from this we can populate data on various third party integration which is most useful case
Very fast time to market in that so many components are available to use immediately.
Error handling mechanisms and patterns of practice are robust and easy to use which in turn has made our application more robust from the start, so fewer bugs.
However, testing and debugging routes is more challenging than working is standard Java so that takes more time (less time than writing the components from scratch).
Most people don't know Camel coming in and many junior developers find it overwhelming and are not enthusiastic to learn it. So finding people that want to develop/maintain it is a challenge.
I cannot speak to this for 2 reasons. 1. I am not privy to the financials associated with this implementation or the previous one. 2. We have not hit our 'go-live' for this implementation yet to compare it's performance to our previous solution.
