Apache Camel vs IBM API Connect

• 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

• The best part is that it is a one-stop solution for hosting all the APIs and keep on increasing as the new ones are added. It has been the leader in our Digital transformation and the features of security, interoperability and accommodating all types of clients based on various technologies has been the greatest asset for us.
• The creation of new API is fairly simple and doesn't require much [of a] learning curve. Once you have created the new API, you can publish it as well to the specific audience and they can try to interact with that API with the required security parameters to get to the actual service back-end.
• The installation is quite straightforward and the product is ready to go. The deployment of the artefacts from environment to the other or code promotion is relatively simple as compared to other older products.
• The Gateway used here is IBM Datapower which is one of the most secure, reliable, highly available, fast and can integrate with almost any front-end or back-end.

Read full review

• I find the "seda" endpoint to be less obvious that it is doing multi-threading than Spring Integration's executor mechanism.
• Integration with Spring Beans is pretty good, but I believe SI's is a bit better (for obvious reasons, both being Spring products).
• SI's use support is probably a bit better/faster and I believe the user base is larger so that there are most questions/answers for SI on StackOverflow

Read full review

• Currently they use 2 portals one for Test and one for Prod. They should merge them now
• We wanted some relation between SSL & the application / organisation created in API connect. I believe it’s now part of API connect V6

Read full review

• Apache Camel is open source and Java based. So if your engineering team is strong in Java this could be a good framework to adopt.
• Apache camel is open source.
• Camel could be run on OSGi containers like Karaf or Fuse.

Read full review

• IBM API Connect has been very beneficial for our business because it has increased the productivity and collaboration to a great extent. All the team members are aware of the method they need to follow to develop new API and check internally if there is already an API existing to replicate that functionality. So, reusability has increased significantly after this and saved us a lot of effort and time.
• The work of the IT Security has lessened because now we don't need to submit IP white-listing requests to them of each new API being developed. If that client is allowed to hit 1 service, he is allowed to hit other services as well as long as he has the proper SSL certs and auth tokens or any other method of authentication used in the service.
• The code promotion and deployment of artefacts has been really smooth and without issues. So, that is a big plus if you consider production deployment going swiftly and hassle-free.

Read full review