Apache Camel vs. SAP Integration Suite

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.

Incentivized

SAP Integration Suite has been helpful to our organization in eliminating manual processes but also to create custom processes that align with business requirements. It has allowed multiple vendors to integration with our SAP products and be housed in one place. The tool requires advanced technical knowledge and/or strong AMS support. I would recommend to ensure you have proper resources aligned prior to implementation.

Incentivized

• 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.

Incentivized

• Broad Connectivity: SAP Integration Suite excels in connecting diverse systems, including SAP and non-SAP applications, databases, and third-party services.
• Pre-built Integrations and Templates:The suite provides a library of pre-built integrations and templates for common business scenarios.
• User-Friendly Design Tools:
• API Management:

Incentivized

• 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

Incentivized

• Could be even more business friendly with programming language abstracted
• Ability to simulate the integration flow instead of a real run
• Have some kind of an AI-assistant suggesting the optimal design of an integration flow as it's being built (best practice assistant)

Incentivized

SAP Integration Suite is very helpful to us in many ways to manage purchase procedures, stocks, and data of vendors and suppliers. Also, it helps to manage data for service providers. SAP Integration Suite has the tool to conduct training and evaluation. Unique features like the cloud can provide access from any place and by any device is very helpful.

Incentivized

It's very easy to use and configure.

Incentivized

Support is hard to reach and takes a long time to get a response.

Incentivized

Work with an SAP implementation partner, if possible.

Incentivized

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.

Incentivized

I selected it because its now one of the best thing to do and to work. As we are currently working from home it makes the work easy and comfortable and yet the main usage will be in office the environment created will be simple. The UI logic is based on some calculations which will rely on some natural intuations of mind and when it comes to mind it is easy.

Incentivized

• 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.

Incentivized

• In the long run will enable us to undeploy our on premise solution
• As long as integration suite doesn't support all capabilities PO has complete migration is hard
• Will probably be cheaper than our on premise solution when we are completely migrated

Incentivized