Apache Camel vs Magic xpi Integration Platform

• 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 UI is really simple to use, you have source / destination mapping for the items.
• The scheduler gives you a lot of options when executing the models.
• The error handling is usually pretty good and the errors can be corrected fast.

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

• Although the scenarios may be online, the main service usually freezes and the processes can't transact any data. With a single restart of the service, the processes will be functioning again.
• The support for more applications would be nice, even though there is a nice number of them.
• The licensing for the software may be a little confusing.

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

• The implementation time for this kind of projects has been greatly reduced.
• Certifying an In-House resource in the Magix xpi platform is probably the best option, considering all of the projects that can be developed in the future without the need of an external consultant.
• The processes that have been automatized with the Magic xpi platform helped reduced human error and the time those processes took to finish.

Read full review