Apache Camel vs Apache Kafka

• 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

• 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.

Read full review

• 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

Read full review

• 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

Read full review

• 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.

Read full review

• 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.

Read full review