Apache Camel is an open source integration platform.
N/A
Informatica MDM & 360 Applications
Score 5.4 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.
N/A
Mule ESB
Score 9.0 out of 10
N/A
Mule ESB, from Mulesoft, is an open source middleware solution.
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.
It is a robust software with great management and data model. It can be difficult to learn how to use and deploy the first time but the mapping and features work very well and have optimized our productivity and cost savings. We can customize reports, create rules and integrate with other applications. Overall I recommend it.
If you’re bringing anything into Salesforce you should just invest now into Mule, you will get your money’s worth and find a myriad of uses to build APIs between many other systems. Once you build a component you can easily reuse it as a building block to attach to another source/destination. This makes it easy to ramp up quickly and spread usage of Mule throughout your enterprise. A good value for medium to large companies, but probably cheaper to outsource your job to a consulting firm if you are smaller.
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 best suited for Rest API development. Mule ESB uses RAML as an API descriptor which is less complex and easy to understand. RAML is an open standard majorly supported by Mulesoft. Once RAML is developed, it is very easy (a few clicks)to create flows corresponding to the resources defined in the RAML. One can also include JSON schema validation in RAML, and with the use of APIkit router, Mule ESB makes the request validation very easy (it's automatic basically.)
Mule ESB comes with a large spectrum of community and enterprise connectors. We have connectors for all the major platforms like Facebook, Twitter, Salesforce, SAP, etc. This enables Mule ESB to integrate with the other systems in a faster and more robust way. Mule ESB has many components to fulfill the requirements of each integration (for example batch processing, parallel processing, choice, etc.)
Mule API gateway is one of the best tools (modules) of Mulesoft's offering. It supports API governance and management very well. One can easily enforce policies on their APIs with API gateway. It enables some of the must-have features in an API solution (i.e. throttling, oAuth, access levels, etc.)
Implementing a CI/CD (DevOps) environment for Mule ESB is a very easy task. Mule majorly uses MAVEN as its build tool, which in turn makes it best suitable for CI/CD approach. Mule also provides MAVEN plugins for auto deployments to the servers. Mule also has a best Unit testing module which is MUnit. MUnit can be used for both Unit and Functional testing, and it is easy to write and generates coverage reports in various formats.
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.
