Apache Camel is an open source integration platform.
N/A
IBM App Connect
Score 9.2 out of 10
N/A
IBM’s App Connect is a cloud-based data integration platform with data mapping and transformation capabilities within connectors between high-volume systems. App Connect also offers near-real time data synchronization and an API builder that is adaptable to the user’s coding skill level.
N/A
Pricing
Apache Camel
IBM App Connect
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache Camel
IBM App Connect
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Apache Camel
IBM App Connect
Considered Both Products
Apache Camel
Verified User
Anonymous
Chose Apache Camel
Easier to use, better routing system, but perhaps too basic dependant on business needs?
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 …
working with Apache's TomCat server, our developer found it most easy given the UI of Camel to perform integration and data processing tasks. when compared to the other two softwares they felt the need to learn new tools outside of Apache family can be avoided and with kafka, …
We did a comparison of the two products with an example application that tested about 10 distinct EIP pattern. We wrote Camel in XML and Java DSL and SI in XML. This was about 3 years ago. At the time, I found the threading model in SI to be more intuitive and Camel's seda. …
Akka or Spring Integration/ XD are alternatives to Apache Camel and very good frameworks on their own (especially Akka which provides a single threaded illusion).
We chose Apache Camel because it was lightweight, easy to get started with and because it had a groovy DSL since we were a grails shop when we started using it.
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.
Esper is only similar in that they both are involved in complex even processing, however Esper's aim is a little more complex and specialized. In general however I found Apache Camel to be much easier to understand, implement and debug, whereas Esper's DSL can get very …
We selected IBM App Connect Enterprise due to our confidence in IBM as a long-term partner and our history with their integration technology (Message Broker/Bus). IBM App Connect provides the robustness and high reliability needed for our core on-premises systems, with proven …
The choice of IBM App Connect was a strategic decision driven by the urgent need for agile, user-friendly, and cost-effective application and data integration. While DataPower, webMethods, and API Connect are powerful tools in their own rights, their primary focuses as security …
IBM App Connect started as MQSeries Integrator (MQSI) more than 20 years ago. In the IT environment, this is like an eternity. And this allowed a lot of customer experience and needs to be embedded in the product. Without it becoming a legacy application. The changes done in …
I used the IBM WebSphere DataStage tool which is an ETL tool where we extract transform and load. This tool is a little tougher to understand than App Connect. For example, to build a job in App Connect is easier than DataStage. We can schedule the job to run in the same …
IBM API Connect is positioned ahead of Apigee in the Gartner report. But in my opinion the development experience and the data transformation capability is way better in Apigee and it’s a proved solution and has a huge client list. (I have worked on an American Express …
We did not select Cast Iron as our iPaaS solution, it was the weakest competitor in the field that we evaluated. Our experience was that it was not nearly as easy to learn, without in-depth training and guidance, and the developer UI was extremely buggy. We subjected each of …
WebSphereCast Iron is preferred for our sales and delivery teams over Informatica. We find the products and teams for WebSphere Cast Iron easier to work with here and find WebSphere Cast Iron better when integrating with non-Salesforce systems. WebSphere Cast Iron struggles to …
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.
IBM App Connect is well-suited to serve as a central integration hub, particularly for scenarios involving data transformation, complex routing logic, and dynamic backend routing. It excels at enabling legacy system modernization and supports real-time, event-driven architectures effectively. However, it is less appropriate for simple point-to-point integrations or for use cases requiring workflow process management and human task orchestration, where BPM or lightweight automation tools may be more suitable.
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.
It is the best on-premise application to cloud integration in the market. I guess IBM is planning to integrate IBM App Connect with the IBM API Connect solution.
You can do some really powerful things with this system. The overall design is an attempt to make configurable some of the routine tasks/common functionality, but allow for development/customization of the core of the application.
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.
We selected IBM App Connect Enterprise due to our confidence in IBM as a long-term partner and our history with their integration technology (Message Broker/Bus). IBM App Connect provides the robustness and high reliability needed for our core on-premises systems, with proven scalability to the cloud. Its key strength is enabling deep integration by combining low-code with the power of complex, custom logic, ensuring the platform's capabilities exactly matched our need to handle complex flows.
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.