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 11)

EIP using Camel

Rating: 8 out of 10
Incentivized
April 03, 2017
Verified User
Engineer in Engineering
Defense & Space Company, 11-50 employees
Vetted Review
Verified User
Apache Camel
3 years of experience
Use Cases and Deployment Scope
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.
Pros
  • 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.
Cons
  • 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
Likelihood to Recommend
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.

Camel is awesome!

Rating: 10 out of 10
Incentivized
April 13, 2017
Verified User
Engineer in Engineering
Financial Services Company, 1001-5000 employees
Vetted Review
Verified User
Apache Camel
2 years of experience
Use Cases and Deployment Scope
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.
Pros
  • 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
Cons
  • Documentation could use some work, sometimes it takes a bit of trial and error to figure out how to do something.
Likelihood to Recommend
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.

Very Good and Lightweight Integration Solution for your Applications

Rating: 9 out of 10
Incentivized
May 06, 2021
Verified User
Analyst in Information Technology
Education Management Company, 10,001+ employees
Vetted Review
Verified User
Apache Camel
6 years of experience
Use Cases and Deployment Scope
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.
Pros
  • 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
Cons
  • 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
Likelihood to Recommend
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.

Apache camel review

Rating: 9 out of 10
Incentivized
July 12, 2016
Verified User
Employee in Engineering
Computer Software Company, 51-200 employees
Vetted Review
Verified User
Apache Camel
1 year of experience
Use Cases and Deployment Scope
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].
Pros
  • 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.
Cons
  • To be able to hot deploy
Likelihood to Recommend
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.

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.
Return to navigation