Apache Camel vs. Make

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Camel
Score 6.3 out of 10
N/A
Apache Camel is an open source integration platform.N/A
Make
Score 9.2 out of 10
N/A
Make (formerly Integromat) automates integration between applications. It features data transformation capabilities within a no-code graphic interface. The former Integromat was acquired by Celonis in 2020, and the current product Make is a Celonis brand.
$9
per month
Pricing
Apache CamelMake
Editions & Modules
No answers on this topic
Free
$0
per month
Core
$9
per month
Pro
$16
per month
Teams
$29
per month
Enterprise
Contact
Offerings
Pricing Offerings
Apache CamelMake
Free Trial
NoNo
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Features
Apache CamelMake
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
Apache Camel
-
Ratings
Make
8.3
5 Ratings
3% above category average
Pre-built connectors00 Ratings9.05 Ratings
Connector modification00 Ratings9.55 Ratings
Support for real-time and batch integration00 Ratings9.54 Ratings
Data quality services00 Ratings8.05 Ratings
Data security features00 Ratings7.54 Ratings
Monitoring console00 Ratings6.55 Ratings
Best Alternatives
Apache CamelMake
Small Businesses

No answers on this topic

Zapier
Zapier
Score 9.0 out of 10
Medium-sized Companies
Boomi
Boomi
Score 8.3 out of 10
IBM App Connect
IBM App Connect
Score 8.9 out of 10
Enterprises
TIBCO B2B Integration Solution
TIBCO B2B Integration Solution
Score 8.0 out of 10
IBM App Connect
IBM App Connect
Score 8.9 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache CamelMake
Likelihood to Recommend
7.9
(11 ratings)
9.0
(5 ratings)
Usability
-
(0 ratings)
9.0
(3 ratings)
Support Rating
-
(0 ratings)
7.3
(2 ratings)
User Testimonials
Apache CamelMake
Likelihood to Recommend
Apache
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.
Read full review
Celonis
Integromat is the best tool for business automation in my opinion because unlike Zapier it allows us to integrate with any API even if the app is not available which allows us to create automation even with the less known apps that we use or the ones that we built internally for our own company.
Read full review
Pros
Apache
  • 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.
Read full review
Celonis
  • UI/UX Simplicity and Features
  • Workflows are explained in details and even people without IT background can use the tool.
  • Consumption is nicely tracked.
  • Myriad of existing templates, solutions, and readymade connectors.
Read full review
Cons
Apache
  • 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
Read full review
Celonis
  • There are always new platforms and connections that we'd like to see
  • More flexibility in paying for operations (tasks) on a sliding scale, instead of by tier
  • More thorough support documentation on connecting various platforms and troubleshooting errors
Read full review
Usability
Apache
No answers on this topic
Celonis
Make's easy to understand user interface helps you to visualize what's happening at all times. Could use some tweaks around the navigation from a scenario specifically in the folders and back navigations. I can't tell you the amount of time wasted in that area. When you branch, you can't bring a branch back together in the same scenario which is kind of a bummer as well.
Read full review
Support Rating
Apache
No answers on this topic
Celonis
The pricing schema is very attractive, almost 50% lower than the competition. You could start from free and then grow. It has a pretty big library of connections to other apps and services, which really helps you when everything is a mess. Integromat has a really easy-to-use interface. You could do almost everything with fewer than 5 clicks. Scenarios (automation steps to complete a routine) have graphics so you can configure them more easily.
Read full review
Alternatives Considered
Apache
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.
Read full review
Celonis
Integromat allows us to do everything we used to do on Zapier but it doesn't limit us to only the popular apps, with Integromat we're integrating custom APIs and we get data from different servers through GET requests and it's exactly what we needed and Zapier couldn't provide it.
Read full review
Return on Investment
Apache
  • 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
Celonis
  • We used too many credits multiple times and had to buy them additionally, there are no prevention systems to setup to alert before it happens.
  • Some consumption is difficult to understand and requires time and digging.
  • It requires heavy internal effort to simplify things in Make in order for it to operate cheaper.
  • Initial IT setup is paramount and determines a lot.
Read full review
ScreenShots