Apache Camel is an open source integration platform.
N/A
Kong Konnect
Score 8.3 out of 10
N/A
Kong Inc. is a cloud connectivity company headquartered in San Francisco. They are the creator and primary supporter of Kong, the open-source Microservice API gateway, and offer Kong Konnect, an enterprise-tier platform that delivers connectivity and visibility for services in multi-cloud environments.
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.
Using Kong [Konnect]'s declarative settings, a user may control traffic, automate deployment, and maintain container-based software after it's deployed. In addition, it handles the whole lifecycle of service management. Installation, management, and operation of Kong [Konnects]'s cloud-native connection runtimes may be performed in any cloud or Kubernetes provider environment, as well as on-premises environments. In order to optimise their services and transactions, users may keep track of their services and transactions in real-time via real-time monitoring.
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.
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.
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.