Apache Camel is an open source integration platform.
N/A
Zapier
Score 9.0 out of 10
N/A
The Zapier Automation Platform designed to integrate data between web apps. It is scaled for small to mid-sized businesses, with a functional but limited free version of the program.
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.
If you have processes that are now managed and controlled using a spreadsheet, Zapier will give you a lot more control over what is happening and will help you increase productivity by eliminating simple steps such as sending emails and sharing information with your colleagues. It frees time for very transactional activities.
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.
Ease of use - multiple people in the organization can set up and run Zaps per their specific use cases without much training.
Connectivity - Zapier is able to connect to multiple applications we use on a regular basis.
Functionality - Zapier provides embedded functionality within the app itself (email, data conversion), but also appropriate triggers and actions for apps it connects to.
Versatile - Zapier can execute complicated and simple tasks and thus has many use cases.
The interface is very user-friendly, and there are also many tools to help a brand-new user get started. For example, you can put your Zap idea into the AI bot, and it will basically build a shell of your Zap to get started on. The format for each step within a Zap is also very helpful (set up the connection/app, set up the fields/details, then test).
Before we purchased Zapier, I contacted support and asked them if Zapier could support my intended workflow (this is actually a selection on their support form - awesome). Within 2 hours, I was contacted by a support team member who seemed sure it would work, but granted me premium access for 2 weeks to try it out for myself. Sure enough, it did! Ever since then, support has replied rapidly to any problems I have experienced and answered my questions within a few sentences.
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.
We actually utilize both Integromat and Zapier at our company, for all the reasons detailed in this review. Though Zapier is excellent for simple client integrations, we often run into internal use cases that require complexity that Zapier cannot provide. Specifically working with API calls (not just webhooks), complex multi-step integrations with Routing/parsing/etc, and large volume integrations. Integromat is perfect for these use cases, but doesn’t provide the simplicity and account scalability that Zapier offers.
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.
