Skip to main content
TrustRadius
Apache Camel

Apache Camel

Overview

What is Apache Camel?

Apache Camel is an open source integration platform.

Read more

Learn from top reviewers

Apache Camel is a mature low cost open source alternative to commercial messaging layer products

Rating: 9 out of 10
August 19, 2022
IncentivizedVetted ReviewVerified User
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 integratio...
Continue reading
Verified user
Professional
Apache Camel1 year of experience

Apache Camel - Integrate lots of things together with custom complex business logic on top

Rating: 7 out of 10
July 25, 2022
IncentivizedVetted ReviewVerified User
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 ...
Continue reading
Verified user
Engineer
Apache Camel2 years of experience

Routing made simple!

Rating: 7 out of 10
June 23, 2022
IncentivizedVetted ReviewVerified User
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...
Continue reading
Verified user
Engineer
Apache Camel1 year of experience

Very Good and Lightweight Integration Solution for your Applications

Rating: 9 out of 10
May 6, 2021
IncentivizedVetted ReviewVerified User
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 ...
Continue reading
Verified user
Analyst
Apache Camel6 years of experience

best lightweight integration solution

Rating: 9 out of 10
March 28, 2017
IncentivizedVetted ReviewVerified User
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 ...
Continue reading
Akmal Muqeeth
Team Lead - Engineering
Lead Software Engineer
Brighter
Apache Camel2 years of experience
Log in with LinkedIn to see content from your network
Return to navigation

Pricing

View all pricing
Apache Camel

Apache Camel

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?

11 people also want pricing

Alternatives Pricing

Cin7

Cin7

$295
per month
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 From Top Reviewers

View all reviews
(1-5 of 6)

Routing made simple!

Rating: 7 out of 10
Incentivized
June 23, 2022
Verified User
Engineer in Information Technology
Financial Services Company, 5001-10,000 employees
Vetted Review
Verified User
Apache Camel
1 year of experience
Use Cases and Deployment Scope
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.
Pros
  • Adding new routes is very easy and efficient
  • Easy to use, easy to get up and running
  • Great integration with java frameworks
Cons
  • The documentation is a little deficient
  • Lacking a framework integration with big data capabilities
Likelihood to Recommend
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.

Apache Camel Review

Rating: 9 out of 10
Incentivized
April 10, 2017
Verified User
Team Lead in Engineering
Financial Services Company, 10,001+ employees
Vetted Review
Verified User
Apache Camel
5 years of experience
Use Cases and Deployment Scope
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.
Pros
  • 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.
Cons
  • 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.
Likelihood to Recommend
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.

Apache Camel: ways you're wasting developer time if you aren't using it

Rating: 10 out of 10
Incentivized
July 12, 2016
DM
David McCann
Senior Software Engineer
Fast Orientation (Computer Software, 11-50 employees)
Vetted Review
Verified User
Apache Camel
2 years of experience
View profile
Use Cases and Deployment Scope
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).
Pros
  • 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.
Cons
  • 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.
Likelihood to Recommend
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.

Better on a Camel

Rating: 9 out of 10
Incentivized
July 15, 2016
SS
Surjit Sen
Senior Software Consultant at Randstad
Cox Communications (Broadcast Media, 10,001+ employees)
Vetted Review
Verified User
Apache Camel
3 years of experience
View profile
Use Cases and Deployment Scope
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.
Pros
  • 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.
Cons
  • 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.
Likelihood to Recommend
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.

best lightweight integration solution

Rating: 9 out of 10
Incentivized
March 28, 2017
AM
Akmal Muqeeth
Lead Software Engineer
Brighter (Internet, 51-200 employees)
Vetted Review
Verified User
Apache Camel
2 years of experience
View profile
Use Cases and Deployment Scope
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.
Pros
  • Producing to and consuming from any messaging system
  • Message type conversion
  • Large support library
Cons
  • Documentation could use some more detail
  • Hot deployment
Likelihood to Recommend
For basic publish subscribe use cases, Apache Camel is the clear winner.
Return to navigation