What users are saying about

Apache Camel

24 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 7.4 out of 101

elastic.io Integration Platform

2 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8 out of 101

Add comparison

Likelihood to Recommend

Apache Camel

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.
No photo available

elastic.io Integration Platform

elastic.io Integration Platform is well suited for developers already leveraging the Elastic Search cluster, who want to automate and simplify add-on integrations. If developers are streaming data between plugins and want to have event-based batching, this is a great product to do that, albeit a paid solution, it can enhance your deployment and automation of ES plugins.
No photo available

Feature Rating Comparison

Cloud Data Integration

Apache Camel
elastic.io Integration Platform
8.0
Pre-built connectors
Apache Camel
elastic.io Integration Platform
7.0
Connector modification
Apache Camel
elastic.io Integration Platform
9.0
Support for real-time and batch integration
Apache Camel
elastic.io Integration Platform
8.0
Data security features
Apache Camel
elastic.io Integration Platform
7.5
Monitoring console
Apache Camel
elastic.io Integration Platform
8.5

Pros

  • The Java DSP is one of the primary reasons we chose Camel over Spring Integration's XML-based route definitions. It provides compile-time checking of syntax with auto-complete in an IDE (Eclipse, etc).
  • The component documentation on the website is phenomenal.
  • Error handling mechanisms are robust and easy to use and set up. Default settings are great and intuitive.
  • The ability to define distinct contexts within the same application and define context-wide, context-specific error handling is great as well.
No photo available
  • Streamlining data directly between relevant ES plugins
  • Automating ES configuration management
  • Batching data relays
No photo available

Cons

  • I find the "seda" endpoint to be less obvious that it is doing multi-threading than Spring Integration's executor mechanism.
  • Integration with Spring Beans is pretty good, but I believe SI's is a bit better (for obvious reasons, both being Spring products).
  • SI's use support is probably a bit better/faster and I believe the user base is larger so that there are most questions/answers for SI on StackOverflow
No photo available
  • Paid solutions are always challenging when the tool itself is free
  • Available training for this paid solution
No photo available

Alternatives Considered

We did a comparison of the two products with an example application that tested about 10 distinct EIP pattern. We wrote Camel in XML and Java DSL and SI in XML. This was about 3 years ago. At the time, I found the threading model in SI to be more intuitive and Camel's seda. However, Camel's documentation at the time was far and away more complete (Wiki pages for Camel vs looking through XML schema for SI). Since the SI has improved their documentation. The main factor that I believe still sets Camel apart is the Java DSL. Writing routes is complicated enough, but doing so in XML would be just painful.
No photo available
There are no comparable ES integration platforms for that I know of, this is the only solution that does what it does at this level.
No photo available

Return on Investment

  • 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.
No photo available
  • If your datasets are diverse and could use automation, this will bring good ROI for time spent
No photo available

Pricing Details

Apache Camel

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Apache Camel Editions & Modules
Apache Camel
Additional Pricing Details

elastic.io Integration Platform

General
Free Trial
Yes
Free/Freemium Version
Premium Consulting/Integration Services
Yes
Entry-level set up fee?
Optional
elastic.io Integration Platform Editions & Modules
elastic.io Integration Platform
On-premise Edition
Dedicated
$01
1. Contact elastic.io for estimation
SaaS Edition
Lean
$5991
Professional
$1,1991
Enterprise
$2,2791
1. per buyer
Additional Pricing Details