Skip to main content
TrustRadius
Apache Camel

Apache Camel

Overview

What is Apache Camel?

Apache Camel is an open source integration platform.

Read more
Recent Reviews

TrustRadius Insights

Apache Camel is widely used as an enterprise integration solution by organizations transitioning from a monolithic to a service-oriented …
Continue reading

Routing made simple!

7 out of 10
June 23, 2022
Incentivized
We use Apache Camel as a bridge between various systems, where implementation and message format is changing fairly often. Integration and …
Continue reading

Camel is awesome!

10 out of 10
April 13, 2017
Incentivized
I've used Apache Camel as a great alternative integration framework compared to heavier middleware solutions from companies like IBM. It …
Continue reading

Apache Camel Review

9 out of 10
April 10, 2017
Incentivized
Apache Camel is being used for multiple projects in different organizations that I have worked at. It is being leveraged for EIP as well …
Continue reading

EIP using Camel

8 out of 10
April 03, 2017
Incentivized
We use it as the processing backbone/Enterprise Integration Pattern (EIP) framework for several products that we develop. It is used to …
Continue reading

Apache camel review

9 out of 10
July 12, 2016
Incentivized
I used it when I worked at Verizon Wireless. We used apache Camel on a couple projects as an integration layer between the UI and backend …
Continue reading
Read all reviews
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Apache Camel?

Apache Camel is an open source integration platform.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

10 people also want pricing

Alternatives Pricing

What is Cin7?

Cin7, headqduartered in Auckland, aims to make complex retail and wholesale simple with all-in-one cloud inventory, POS, EDI and 3PL. Cin7 allows users to manage sales channels, inventory, point of sale and supply chain in one central, cloud-based software. Cin7 offers integrations using third…

Return to navigation

Product Details

What is Apache Camel?

Apache Camel Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(34)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Apache Camel is widely used as an enterprise integration solution by organizations transitioning from a monolithic to a service-oriented architecture. Its lightweight nature, ease of use, and implementation of existing integration patterns make it a popular choice. Users praise Apache Camel for its groovy DSL, which simplifies the process of connecting microservices and enabling the publish-subscribe pattern by consuming from and producing to AWS SQS queues.

Quartz jobs heavily rely on Apache Camel for seamless integration, and Cox Communications utilizes this product in various departments to provide quick and scalable integration of diverse business systems. By reducing development effort and resources, Apache Camel fits well within Cox's existing infrastructure and is often used alongside customized versions of Camel components. In product development teams, Apache Camel is essential for core event processing, facilitating interactions over JMS between different modules while handling marshaling, unmarshaling, and sending/receiving POJOs.

With its plethora of plugins for various connectors and a user-friendly experience, Apache Camel serves as an alternative integration framework to heavier middleware solutions. It acts as a component of an Enterprise Service Bus, defining message routing and transformation rules for integrating on-premise applications and cloud services. Moreover, Apache Camel bridges systems with changing implementations and message formats, enabling seamless integration and workflow pipelines. Teams appreciate the time-saving and scalable nature of this product, making it a preferred choice in multiple organizations for EIP and event-based code projects. Lastly, Apache Camel proves to be vital as an integration layer between UI, backend services, and databases using its REST component and XML/Java DSL solutions.

The open-source nature of Apache Camel particularly shines when performing daily integration activities in non-production environments. It offers a reliable platform for deriving code from files based on defined logic and processes. Additionally, Apache Camel handles error handling with built-in features like error retry, waiting, and exponential backoff. This makes it the go-to choice for integrating multiple sources and sinks of data with different formats and protocols, allowing for the implementation of complex logic. Overall, Apache Camel is highly regarded for its ability to simplify integration activities and enable seamless connectivity across various systems and platforms.

Easy Learning Curve: Several users have found Apache Camel to have an easy learning curve, allowing them to quickly grasp the concepts and start using it efficiently.

Extensive Integration Support: Many reviewers have praised Apache Camel for its extensive support for integration with diverse software platforms. With over 150 components available, users can seamlessly integrate Camel with various frameworks and middleware products such as Spring, Apache Karaf, and Servicemix.

Robustness and Reliability: Numerous users have highlighted the robustness of Apache Camel in handling various information transfer protocols out-of-the-box. They appreciate that it is a reliable solution for their integration needs, making it suitable for creating microservices and handling complex business logic.

Lack of Detail in Documentation: Several users have found the documentation to be lacking in detail and feel that it could use improvement. They mention that sometimes it takes trial and error to figure out how to do something, indicating a need for more comprehensive instructions.

Steep Learning Curve: Users have mentioned that there is a relatively steep learning curve associated with using the software. Some users felt overwhelmed by the complexity and required a significant amount of time and effort to become proficient in its usage.

Dependence on Java Skills: A common concern expressed by users is the heavy dependence on Java skills for optimal use of the software. Many users feel that a great skill set in Java is required to effectively utilize all the features and capabilities offered by the software.

Users have praised Apache Camel as an excellent choice for beginners in integration software development. They have found it to be user-friendly and valuable when starting out in this field. Reviewers also recommend utilizing online videos for additional assistance with Apache Camel. Video tutorials offer helpful insights and explanations. Another common recommendation is to consider Apache Camel as a viable alternative to larger middleware options like IBM. Users appreciate its flexibility and simplicity compared to more complex and expensive alternatives. It is also advised to have a clear understanding of EIPS (Enterprise Integration Patterns) when using Apache Camel. Additionally, users suggest keeping routes small and limiting the number of threads on endpoints to prevent idle threads from consuming locks.

Reviews

(1-11 of 11)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Apache Camel is used to provide a component of our Enterprise Service Bus, we use it for defining message routing and transformation rules, enabling the business to integration disparate on premise applications and cloud services in a robust and relatively low effort way. Our primary pattern for integration that we use is asynchronous messaging exchanged via an Enterprise Service Bus.
  • Rules for routing messages between senders and receivers
  • Applying transformations to messages
  • Low cost low effort solution
  • Open source solution relies on community for support
  • Lacks graphical user interface for message routing and transformation definitions
  • Relatively steep learning curve
Apache Camel is a very mature open source solution for implementing enterprise integration patterns, and is good for organizations that are comfortable using open source solutions with only community support that need the ability to route and transform messages between senders and receivers connected to an enterprise message bus solution with no licensing costs.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We had some workloads where we need to integrate multiple sources & sinks of data, with different formats & protocols, while doing some pretty complex logic on top of that. Apache Camel was a natural choice for it since there are tons of built-in components that allow making easy connections to all the sources & sinks that we need. On the other hand, the Java-native nature of Apache Camel means writing & testing whatever logic we need is just business-as-usual for the engineers.
  • Easy & reliable integration with lots of types of source or sink of data.
  • Complex business logic could be written in Java.
  • Excellent unit testing support with Java.
  • Documentation could be improved
  • Support for complex & advance integration options could be better
  • Navigating the Java code base requires learning curve
There are tons of integration technologies available, the point is to pick the one most suited for your use case. Apache Camel offers easy connections to lots of types of sources or sinks of data while supporting custom complex business logic, all testable. However, it means configuring using Java source code, which is a hurdle when all your logic need is very simple. There are many other GUI-based integration technologies that get those types of logic-lite work done faster.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We use Apache Camel as a bridge between various systems, where implementation and message format is changing fairly often. Integration and tasks workflow pipeline. This system allows for fast and scale able integrations and deployment. This has saved us man time and power.
  • Adding new routes is very easy and efficient
  • Easy to use, easy to get up and running
  • Great integration with java frameworks
  • The documentation is a little deficient
  • Lacking a framework integration with big data capabilities
Could be used to trigger batches and do large-scale processing, using its throttling. We have lots of end-points where the system needs to talk and pass the request to get the response. Using Apache camel it is extremely easy to configure and implement such business requirements. However, the drawback is you need someone in your team to understand and code for Apache Camel.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
My team uses Apache Camel as a Platform as a Software service in the tech stack to perform integration of their code on a component basis by deriving it from files based on a defined logic and processes and then make those available to testers and UAT group. Apache Camel being opensource is very helpful for our team to perform their daily integration activities in non prod environment for quick testing of their work.
  • open source and a great set of component feature set - always latest features available for integration
  • works well with spring boot
  • great community and support for any kind of workflow
  • based on enterprise integration patterns which helps our developers achieve integration tasks with all kinds of API services
  • 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
very well suited when data has to be extracted in itself from files based on defined logic and process workflows and integrated with other processes and applications in your architecture. Our teams put a gateway in front of the APIs for integrating data and ensuring data integrity before letting the application process the data.
April 13, 2017

Camel is awesome!

Score 10 out of 10
Vetted Review
Verified User
Incentivized
I've used Apache Camel as a great alternative integration framework compared to heavier middleware solutions from companies like IBM. It serves that purpose wonderfully, and is a total pleasure to use. Great plugins for almost any connector you could need, and they all work as expected.
  • Open source, which is vitally important
  • Great integration with Java frameworks such as Spring Boot, allowing it to be deployed however you need to deploy it
  • Wonderful testing tools as part of the framework
  • Documentation could use some work, sometimes it takes a bit of trial and error to figure out how to do something.
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.
April 10, 2017

Apache Camel Review

Score 9 out of 10
Vetted Review
Verified User
Incentivized
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.
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.
April 03, 2017

EIP using Camel

Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use it as the processing backbone/Enterprise Integration Pattern (EIP) framework for several products that we develop. It is used to provide components for message ingest, orchestration and export. By orchestration, I mean the determination and execution of the path of any single message through the application. It also is our primary error handling mechanism as it provides out-of-the-box error retry, waiting and exponential backoff.
  • 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.
  • 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
Message processing, especially with high throughput, is an excellent use case. File system monitoring, JMS ingest, etc., is really great. I would most consider it for automated processing scenarios. Although it provides components to support REST endpoints, I would choose frameworks such as Jersey or Spring REST for that. Although it supports a response mechanism, I don't think I would choose to use it in systems where I need fine-tuned control of responses.
Akmal Muqeeth | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
When we switched from a monolithic architecture to a service oriented one we were researching on all the enterprise integration technologies. We chose Apache Camel because it was lightweight, was easy to get started with, had a groovy DSL and because it was an implementation of existing integration patterns. Over the last few years, Apache Camel became the glue that binds all our micro services. We use publish-subscribe pattern the most i.e consuming from and producing to AWS SQS queues. A lot of our quartz jobs are heavily depended on Apache Camel as well. I would highly recommend Apache Camel as a lightweight yet formidable enterprise integration solution.
  • Producing to and consuming from any messaging system
  • Message type conversion
  • Large support library
  • Documentation could use some more detail
  • Hot deployment
For basic publish subscribe use cases, Apache Camel is the clear winner.
July 15, 2016

Better on a Camel

Score 9 out of 10
Vetted Review
Verified User
Incentivized
Apache Camel is used by many departments at Cox Communications, but not the entire organization. It enables quick and scaleable integration of diverse business systems at Cox and reduces development effort and resources. Various Camel components are used and there is even a customized version of Camel Http4 component. Also Camel fits well in the existing infrastructure at Cox.
  • 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.
  • Camel features and documentation can get confusing to new users. Documentation can and should be improved. Also it would help if there are more tutorials available. Certification in Camel and related technologies like Servicemix and Karaf would also help.
  • The Camel infrastructure probably needs to be rebuilt (hopefully this may happen with version 3.0). At this time the latest production release of Camel (2.17.x) is not built with the latest version of Java (JDK 1.8).
  • Camel should also move towards becoming a "heavyweight" ESB product, though this may detract from some of its desirable features.
Apache Camel is well suited for integration of existing software programs/components with newer and external systems. It supports SOAP and REST protocols pretty well. It was not designed to directly support front end systems. It has limited to non-existent support for Javascript. It is not suitable for creating simple standalone applications and meaningful deployment does require use of other frameworks like Spring/Karaf/JBoss.
David McCann | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
I worked on a product development team creating an enterprise cybersecurity product. The core event processing mechanism of the product used Apache Camel in many places, mainly to handle interactions over JMS between the various modules of the product. Apache Camel especially makes the process of sending a POJO from one method to another across two separate application components, handling the marshaling and unmarshaling via JAXB, and the sending and receiving via JMS. It achieves all this routing via a simple XML configuration that is part of the application's spring context (although it can also be configured procedurally).
  • Configuration of information routing via XML in a Sprint Context.
  • Robustness. Apache Camel is capable of handling many different information transfer protocols out-of-the-box.
  • Extensibility. Apache Camel also allows for custom routing handlers where needed.
  • Some of the documentation is a little sparse. In particular, its TCP-based routes use an underlying Netty server, and the interactions between Netty's decoder capabilities and Apache Camel's routing/handler capabilities can be a little muddy at times. In general it is clear which routes and endpoints are the more frequently used and which haven't been given as much attention.
In my experience, Apache Camel was very useful for the main use case that we leveraged it for, i.e. wiring up JMS messaging. I found the less-frequently-used handlers and endpoints to be either less reliable, maintainable, or easy to work with than just rolling my own data transfer logic. I would stick to straightforward use cases where the XML configuration conveys the intent in a very clear manner, and avoid using Apache Camel to do large portions of moving data around that involve business logic or custom intermediaries.
July 12, 2016

Apache camel review

Score 9 out of 10
Vetted Review
Verified User
Incentivized
I used it when I worked at Verizon Wireless. We used apache Camel on a couple projects as an integration layer between the UI and backend services and databases. We used Apache Camel's REST component. We used it as xml and java dsl [solution].
  • It uses URIs to directly integrate with various back-end components.
  • It has a very easy to use REST component.
  • Easy to track the execution flow while coding by using routers.
  • Helps keep different components separate.
  • To be able to hot deploy
If you want to integrate several applications with different protocols and technologies you should use Apache Camel. The good thing about it is that you have to follow same steps for every integration. If you want to have a container you need to use something else.
Return to navigation