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.
In our experience, the product performs really well when interfacing systems with ERP's through SQL server database tables, but we've even made some interfaces with the web service functionality included with the magic xpi integration platform. Also, we've made some SAP Business One - SAP Business One interfaces, for copying information from one company to another.
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.
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.
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.
Honestly, we have only used and evaluated magic xpi platform because of the recommendation of our SAP Business One main supplier, who has previously used the platform for their developments. So far, we have no regrets with the acquisition of the platform and we are very happy with it's performance until now.
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.
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.
