Apache Camel Review
Updated April 10, 2017

Apache Camel Review

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Apache Camel

Apache Camel is being used for multiple projects in different organizations that I have worked at. It is being leveraged for EIP as well as writing event based code.

I worked for an organization that used Camel with Karaf (OSGi) and other organizations where Camel was used just as an open source framework.
  • EIP - enterprise integration patterns. Read events from queue, route to different processes and work on the messages.
  • REST APIs- Apache CXF is used and Camel could be used to provide endpoints.
  • Batches - Camel could be used to trigger batches and do large scale processing, using its throttling. It provides lots of connectors to work with.
  • I feel that Apache Camel is lacking a Spring XD like framework integration with big data capabilities.
  • Apache Camel seems to be very dependent on Spring.
  • 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.
Akka or Spring Integration/ XD are alternatives to Apache Camel and very good frameworks on their own (especially Akka which provides a single threaded illusion).
Camel is very suited where ever you want to use enterprise integration patterns like endpoint integration, routers, aggregators, splitters etc. Also Camel can be used for REST endpoints, designing event driven systems and integration with queues and it provides whole lot of connectors for integration with social etc.