What users are saying about
27 Ratings
59 Ratings
27 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8 out of 100
59 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.9 out of 100

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.
Anonymous | TrustRadius Reviewer

Apache Kafka

Despite the disadvantages I list, I really believe that Kafka is the right choice whenever you need a queueing or message broker system. Kafka is way too battle-tested and scales too well to ever not consider it. The only exception is if your use case requires many, many small topics. Also, Kafka doesn't support delay queues out of the box and so you will need to "hack" it through special code on the consumer side.
Anonymous | TrustRadius Reviewer

Pros

Apache Camel

  • 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.
Surjit Sen | TrustRadius Reviewer

Apache Kafka

  • Apache Kafka is able to handle a large number of I/Os (writes) using 3-4 cheap servers.
  • It scales very well over large workloads and can handle extreme-scale deployments (eg. Linkedin with 300 billion user events each day).
  • The same Kafka setup can be used as a messaging bus, storage system or a log aggregator making it easy to maintain as one system feeding multiple applications.
Anonymous | TrustRadius Reviewer

Cons

Apache Camel

  • 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
Anonymous | TrustRadius Reviewer

Apache Kafka

  • Still a bit inmature, some clients have required recoding in the last few versions
  • New feaures coming very fast, several upgrades a year may be required
  • Not many commercial companies provide support
Juan Francisco Tavira | TrustRadius Reviewer

Likelihood to Renew

Apache Camel

No score
No answers yet
No answers on this topic

Apache Kafka

Apache Kafka 9.0
Based on 1 answer
Kafka is quickly becoming core product of the organization, indeed it is replacing older messaging systems. No better alternatives found yet
Juan Francisco Tavira | TrustRadius Reviewer

Support Rating

Apache Camel

No score
No answers yet
No answers on this topic

Apache Kafka

Apache Kafka 8.8
Based on 6 answers
We are using the Apache open source version of Kafka. The community is a good place to ask questions. and we can get most of our problems resolved there.
Anonymous | TrustRadius Reviewer

Alternatives Considered

Apache Camel

We chose Apache Camel because it was lightweight, easy to get started with and because it had a groovy DSL since we were a grails shop when we started using it.
Akmal Muqeeth | TrustRadius Reviewer

Apache Kafka

I would only use RabbitMQ over Kafka when you need to have delay queues or tons of small topics/queues around.I don't know too much about Pulsar - currently evaluating it - but it's supposed to have the same or better throughput while allowing for tons of queues. Stay tuned - I might update this review after we finish evaluating Pulsar. It's much less battle-tested though.
Anonymous | TrustRadius Reviewer

Return on Investment

Apache Camel

  • Apache Camel is open source and Java based. So if your engineering team is strong in Java this could be a good framework to adopt.
  • Apache camel is open source.
  • Camel could be run on OSGi containers like Karaf or Fuse.
Anonymous | TrustRadius Reviewer

Apache Kafka

  • Positive impact on ROI since now we can use one large deployment of Apache Kafka that can be used for multiple scenarios ( storage systems, log aggregate, messaging queue ).
  • It is open-source so there are no licenses or subscription fees reducing the cost of deployment.
  • Data can now be ingested and analyzed in real-time making it easy to fine-tune the customer experience and decision making for internal IT.
Anonymous | TrustRadius Reviewer

Pricing Details

Apache Camel

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Apache Kafka

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Add comparison