Apache Camel vs Informatica Data Archive

• 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.
• Camel is also good for creating microservices.

Read full review

• Data crunching on housing markets
• Management of internal data usage
• The tech is still very new to our company and as such we are still seeing where it can be of use.

Read full review

• I find the "seda" endpoint to be less obvious that it is doing multi-threading than Spring Integration's executor mechanism.
• Integration with Spring Beans is pretty good, but I believe SI's is a bit better (for obvious reasons, both being Spring products).
• SI's use support is probably a bit better/faster and I believe the user base is larger so that there are most questions/answers for SI on StackOverflow

Read full review

• As a standalone tool (without PowerCenter), ILM does not add much value.

Read full review

• Apache Camel is open source and Java based. So if your engineering team is strong in Java this could be a good framework to adopt.
• Apache camel is open source.
• Camel could be run on OSGi containers like Karaf or Fuse.

Read full review

• Tracking the usage of specific brackets of data across the entire organisation has now become possible.
• The team was already using PowerCenter. Therefore, using ILM was a very apt decision that allowed easier management of data at the organisation level.

Read full review