Apache Camel vs. frends eiPaaS by HiQ

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

Hybrid Integrations: Organizations operating with a combination of on-premises and cloud applications will find frends particularly valuable. Its hybrid integration capabilities ensure seamless data flow between these diverse environments. Both for scheduled integrations that are triggered regularly or for event and API-based integrations. High volume of simple integrations: the pricing model is not tied to the number of integrations like in many competing products.

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

• It has been very stable and reliable over time
• The developer tools are simple to use
• It offers out of the box tasks/activities for typical routine tasks

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

• The recently renewed user interface has not been as clear as the previous version
• Sometimes the performance or capacity has been at limits with more complex integrations

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

frends does not have as broad functionality but it's lightweight and easy to use and has enough features for most integration needs. For example the frends API Management exists but it does not offer lot of options. frends might not be the choice for the largest enterprises but for small and mid sized organizations it does everything you will probably need. They have also recently improved their training materials to help new developers get on board.

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

• Pricing model suites us very well as it is not tied to number of integrations or users. It's much more economic than most well-known competitors
• The stability of the service is crucial and has served as well. We run hundreds of processes on the platform daily and they are really important for other operations.

Incentivized