Apache Camel vs webMethods Trading Network

• Open source, which is vitally important
• Great integration with Java frameworks such as Spring Boot, allowing it to be deployed however you need to deploy it
• Wonderful testing tools as part of the framework

Read full review

• Document tracking
• Efficient partner management
• Set up trading partners with connectivity information

Read full review

• Camel features and documentation can get confusing to new users. Documentation can and should be improved. Also it would help if there are more tutorials available. Certification in Camel and related technologies like Servicemix and Karaf would also help.
• The Camel infrastructure probably needs to be rebuilt (hopefully this may happen with version 3.0). At this time the latest production release of Camel (2.17.x) is not built with the latest version of Java (JDK 1.8).
• Camel should also move towards becoming a "heavyweight" ESB product, though this may detract from some of its desirable features.

Read full review

• Certificate management
• More document types support is needed
• More DB types support

Read full review

• 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

• Increased order processing
• Resubmission of data
• Increased revenue
• Automated data exchange

Read full review