Apache Camel vs. Workato

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

Workato is brilliant to make separate applications work together without much effort or specialists being needed. When specific events on software A should trigger actions on B (or more) and you want that to happen without any development or big budgets, that's where Workato comes into play. It's a great help if you want tasks automated, communications flowing and data synced between different applications.

• 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

• The Workato product interface is brilliantly thought through and designed. The learning curve for first timers is easy enough to get started and build useful things, and Workato really shines in their ability to handle complex triggers and interactions. Workato allows people to build software apps so much faster than by coding each functionality.
• Workato has fantastic documentation, making things accessible without any holes in the product. The product just works, never has any bugs, never lags, and just generally allows us to see and change exactly what we need to.
• Workato has an absolutely amazing support team. We tried the free version for a while, then realized it was the single most important software tool we have, and we upgraded. The support at the paid tier is A+, seriously the best from any company we've worked with. Feels more like a good friend then a support rep.

• 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

• Customer support - responsive, but often not equipped to help efficiently identify root cause of issue. Need to improve escalation to technical resources and turnaround time
• Recipe organization and sharing. Can be challenging to copy recipes, or grab recipes from publicly available site. There are often dependencies and errors that have vague descriptions.

Incentivized

We need to develop Enterprise Application Integrations and Workato was not designed for this

Due to prebuilt recipes, Workato is easy to learn and use for non-technical users if their use case fits the existing recipes. It is not easy for non-technical users to create, modify, debug or maintain complex integrations that are outside the prebuilt recipes.

They employ an extremely knowledgeable team of problem solvers. I've never had a disappointing interaction or one that has left me still searching for answers. I know that when I ask for help, they'll partner with me until we find a solution together

Incentivized

We discovered that we could not use Workato for our more complex, large enterprise integrations. It was useful for simple workflows that matched the prebuilt recipes.

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

We already used Zapier, but since it doesn't support NetSuite we had to choose another automation platform. Now that we've been using Workato for a few months, we have plans to move the stuff we're going through Zapier to Workato. We set up a trial account with all the other platforms, and they were all more expensive and A LOT more complicated than Workato.

• 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

• As business consultants, Workato has greatly improved our offerings to our clients as well as improved the time frame to implement automated workflows and integrations.
• For our clients, the return on investment is almost immediate. Once a Workato recipe is up and running (which can be done very fast), data is integrating, duplicate data entry and user errors are eliminated, and cross-company KPI metrics are easier to report than ever.