Apache Camel vs. Informatica B2B Data Exchange (legacy)

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.

Incentivized

Ideal tool for exchanging data across varying connections and platforms.

Incentivized

• open source and a great set of component feature set - always latest features available for integration
• works well with spring boot
• great community and support for any kind of workflow
• based on enterprise integration patterns which helps our developers achieve integration tasks with all kinds of API services

Incentivized

• Multiple connector options
• Ability to map data across varying platforms
• Ability to introduce transformative code as part of the exchange process

Incentivized

• Some of the documentation is a little sparse. In particular, its TCP-based routes use an underlying Netty server, and the interactions between Netty's decoder capabilities and Apache Camel's routing/handler capabilities can be a little muddy at times. In general it is clear which routes and endpoints are the more frequently used and which haven't been given as much attention.

Incentivized

• Access to and responsiveness of support

Incentivized

Apache Camel has been the integration framework of choice, but I was not the person to make the decision to use it. Compared to other competing products like Tibco Business Works, etc., it is free and open source and its licensing policy is acceptable to the management of Cox.

Incentivized

Selected Informatica B2B Data Exchange primarily due to ease of navigation and overall familiarity.

Incentivized

• 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.

Incentivized

• Allows us to replace complex code and programmers

Incentivized