Likelihood to Recommend 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.
Read full review IBM API Connect is a great tool for interface analysis and for tracking API usage and activity. I can use the IBM API with different products and apps, which further proves its versatility. Even if IBM API is excellent and helpful, there are situations when its sophisticated features are difficult to comprehend. Additionally, IBM API Connect subscription and licensing can be prohibitively expensive at times.
Read full review Pros 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 Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy. Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises. API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth. Read full review Cons didn't work well when our developers tried to transform heavy data sets Apache Camel's whole logic is based on java so team needs to have a great skill set in java if there are a handful of workflows then Apache Camel's full potential can't be realized Read full review The documentation is really frustrating. It does not cover enough functionalities with examples. A whole 100 pages long documentation should be available on gateway scripts. Each component is viewed individually, there is so much need for documentation on common pattern designs and how to implement them ourselves. When you are modifying an API and using the test tab, it can takes a lot of time for the actual change to be updated. Please put a simple check to make us know if the latest change was taken in account. It sometimes can take up to 30 seconds, which is WAY to long when you are putting 4 hours straight of developing and making change every 20 seconds. 500 internal errors are killing me. Please find a way to handle javascript errors Too few policies available. Nothing to handle arrays of jsons. More videos. Youtube is full of "why API Connect is useful" but nothing is on actual API Creation. Is it lame, too much goes into marketing and nothing is left for actual users. IBM have way too many tools and name. When we are using google to search for one of your product we fall on the wrong documentation most of the time. Why writing "IBM API Connect" leads me to 3 different products ?? Read full review Usability It is an extremely easy platform to manipulate and productively develop. The IBM API Connect features and dashboard are very easy to access, and the navigation strategy is also cost-effective. IBM API Connect offers some capabilities that simplify the entire development operations while providing the most accurate and profitable data results, and the development project management is amazing.
Read full review Alternatives Considered 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 .
Read full review IBM API Connect and
Apigee are both robust API management platforms. IBM API Connect was selected for its strong integration capabilities, hybrid cloud deployment options, and comprehensive analytics. It aligns well with organizations seeking flexibility and control over their API ecosystems, especially when dealing with complex integration scenarios across diverse environments.
Read full review Return on Investment 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. Read full review API management and versioning becomes very easy. Plus due to the multiple types of authentication, it is more secure. Requires heavy hardware which can increase the overall cost. Though setting it up is a very complex task, it is a very reliable and efficient API management tool. Read full review ScreenShots IBM API Connect Screenshots