Name: Apache Camel
Rating: 6.3 (34 reviews)
Author: Apache

Help Desk

Web and Video Conferencing

Customer Support

Chatbot

Feature Management

Performance Testing

Development

Business Intelligence (BI)

Calibration Management

Collaboration

Embedded Business Intelligence (BI)

Enterprise Search

Enterprise

Accounting

Accounting and Tax Services

Financial Risk Management

Payment Gateway

Finance and Accounting

Applicant Tracking

Corporate Learning Management

Course Authoring

Employee Performance Management

HR Management

On-Demand Payment

Payroll

Relocation

Resume Parsing

Talent Intelligence

Talent Management

Video Interview

Workforce Analytics

Workforce Management

Human Resources

3D Printing

Cloud Migration

Cloud Storage

Component Content Management

Configuration Management

Database DevOps

Disk Cloning

Fraud Detection

IT Professional Services

Integration Platform as a Service (iPaaS)

Interoperability

Metadata Management

Network Performance Monitoring

Product Implementation Services

Remote Desktop

Remote Monitoring and Management

Secure Email Gateway

Server Virtualization

Test Management

User Virtualization

Information Technology

A/B Testing

Ad Serving & Retargeting

All-in-One Marketing

Content Management

Email Marketing

Enterprise Marketing Management

Event Management

Marketing Automation

Social Media Management

Survey & Forms Building

Web Analytics

Wholesale Marketplace

Marketing

Project Management

Professional Services

Customer Relationship Management (CRM)

Lead Generation

Sales Enablement

Sales Training

Sales

Secure Service Edge (SSE)

Security

Car Rental

Construction Takeoff and Estimating

Direct Secure Messaging

Home Health Care

Insurance Agency Management

Intelligent Document Processing

Medical Office EMR & EHR

Population Health Management

Vertical-Specific

Find top rated software and services based on in-depth reviews from verified users. 400+ software categories including PaaS, NoSQL, BI, HR, and more.

Mule ESB

Salesforce

Apache Kafka

Apache

WSO2 Enterprise Service Bus

WSO2

Azure Logic Apps

Microsoft

Apache Spark

Apache Airflow

Drools

Open Source

Boomi

Kong Gateway Community (Open Source)

Kong, Inc

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.

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.

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.

Apache Camel is an open source integration platform.

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 party logistics (3PL) interface and electronic data interchange (EDI), catering for businesses increasing trend to sell globally.

Ecommerce

Wholesale

Multichannel

Ecommerce Plus

Wholesale Plus

Multichannel Plus

Cin7

Apache Camel

Electronic Data Interchange (EDI) is software that serves to mediate between two separate and often already existing programs. Typically, EDI programs provide messaging services so that different applications can communicate.

Electronic Data Interchange (EDI)

Likelihood to Recommend

The Apache Software Foundation provides support for the Apache community of open-source software projects. The Apache projects are characterized by a collaborative, consensus based development process, an open and pragmatic software license, and a desire to create high quality software that leads the way in its field.

We consider ourselves not simply a group of projects sharing a server, but rather a community of developers and users.

webMethods Trading Network, disc

IBM webMethods

Azure Service Bus

Apache Camel 2021-08-12 21:38:12

Wrike

IBM App Connect

Device42

Apache Camel 2022-06-21 09:16:27

Atlassian Bitbucket

IntelliJ IDEA

Microsoft Visual Studio Code

Apache Camel 2022-07-22 05:43:43

RabbitMQ

Apache Camel 2021-05-01 14:11:03

Amazon S3 (Simple Storage Service)

Amazon CloudSearch

GoDaddy Container-as-a-Service (ElasticHosts, Springs.io), discontinued

Lead Software Engineer

Apache Camel 2017-03-28 12:52:47

TrustRadius is a technology and business research firm based in Austin, Texas. The company is known as a review platform for verified B2B technology and software reviews through a proprietary algorithm and human verification.

TrustRadius

Trial and error

User guide

Get confusing

Graphical user interface

Difficult for beginners

Non native

New users

Steep learning curve

Deployment process

Enough to make

Open source

Error handling

Large scale

Easy to use

Auto complete

Rest apis

Testing tools

Easy learning curve

Source tool

Well documented

Home

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

Message routing
Message transformation
Maturity

Enabled business to integrate disparate systems at relatively low cost
Required a relatively steep learning curve for resources to learn
Few expert resources are available on the market leading to senior resources being expensive

webMethods Trading Network, webMethods.io Integration (webMethods Integration Cloud), Azure Service Bus and Azure Logic Apps

webMethods Trading Network, webMethods.io Integration (webMethods Integration Cloud), Azure Service Bus, Azure Logic Apps

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

Ease of use
Lightweight
XML and Java based configuration is supported.
The routing engine is superb

Very lightweight and basic tool
Does not allow for greater customization

We had some workloads where we need to integrate multiple sources &amp; sinks of data, with different formats &amp; 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 &amp; sinks that we need. On the other hand, the Java-native nature of Apache Camel means writing &amp; 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

Built-in components
Java-native nature
Configuration-as-code

We got all diverse sources & sinks integrated.
We got our complex business logic implemented.
All things checked in to SCM & unit-tested.

IntelliJ IDEA, Bitbucket, Microsoft Visual Studio Code

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

handle multiple workflows
data distribution
modernizing legacy apps and APIs
Process web-submitted forms and generating reports

huge cost saving and quick turn around in terms of extracting data from files and integrating them to our processes
ease the work with java objects
modernizing our API services
ease of using it with Apache's TomCat server

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

When we were looking to move to a service oriented architecture, Apache Camel got us started quickly. It continues to be the backbone of our integration.

Springs.io, Amazon CloudSearch, Amazon S3 (Simple Storage Service)

Apache Camel

Overview

What is Apache Camel?