Talk:Apache Camel

Sorry...

I'm sorry... but what is it used for? —Preceding unsigned comment added by 193.6.138.86 (talk) 15:50, 7 May 2010 (UTC)

As a 2nd year junior developer, I can say that the description in this article might as well have been written in clingon. I'm still trying to figure out what exactly this project is supposed to provide... 67.137.121.106 (talk) 16:25, 24 May 2011 (UTC)

This is a blanket problem for all Java and web app-related information. I call it self-referential documentation. I don't know if there's a solution. Maybe we need to go through all of the article one-by-one and add summaries that aren't written in Klingon. Mithunc (talk) 17:41, 1 September 2011 (UTC)

Routing and mediation rules?

Follow-up to above posting: the page should at minimum describe (or provide links to) what are "routing and mediation rules".

Blacklisted Links Found on the Main Page

Cyberbot II has detected that page contains external links that have either been globally or locally blacklisted. Links tend to be blacklisted because they have a history of being spammed, or are highly innappropriate for Wikipedia. This, however, doesn't necessarily mean it's spam, or not a good link. If the link is a good link, you may wish to request whitelisting by going to the request page for whitelisting. If you feel the link being caught by the blacklist is a false positive, or no longer needed on the blacklist, you may request the regex be removed or altered at the blacklist request page. If the link is blacklisted globally and you feel the above applies you may request to whitelist it using the before mentioned request page, or request it's removal, or alteration, at the request page on meta. When requesting whitelisting, be sure to supply the link to be whitelisted and wrap the link in nowiki tags. The whitelisting process can take its time so once a request has been filled out, you may set the invisible parameter on the tag to true. Please be aware that the bot will replace removed tags, and will remove misplaced tags regularly.

Below is a list of links that were found on the main page:

• http://architects.dzone.com/articles/apache-camel-integration

  Triggered by \bdzone\.com\b on the global blacklist

• http://refcardz.dzone.com/refcardz/enterprise-integration

  Triggered by \bdzone\.com\b on the global blacklist

If you would like me to provide more information on the talk page, contact User:Cyberpower678 and ask him to program me with more info.

From your friendly hard working bot.—cyberbot II ^Notify_Online 18:47, 8 December 2013 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified one external link on Apache Camel. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20080915035805/http://wiki.open-esb.java.net:80/Wiki.jsp?page=CamelSE to http://wiki.open-esb.java.net/Wiki.jsp?page=CamelSE

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 07:55, 16 October 2016 (UTC)

Proposed expansion of Apache Camel article (currently a stub)

Hi, I'm proposing an expansion of this article, which has been tagged as a stub since 2015 and has only 2 citations. I have a COI disclosure on my user page as I'm a contributor to the project.

The proposed changes add: a History section, Architecture overview, Community and development statistics (sourced from OpenHub and Stack Overflow), an Adoption section with 6 notable deployments (all cited from Computerworld, Red Hat case studies, and conference records), and an Ecosystem section covering related subprojects.

All claims are supported by 14 third-party citations. I've avoided promotional language and kept the tone encyclopedic.

I've posted the proposed text below for review before making any edits. Happy to adjust based on feedback.

---

```wiki

Apache Camel
Developer	Apache Software Foundation
Release	June 27, 2007 (2007-06-27)
Stable release	4.18.2 LTS / May 28, 2026 (2026-05-28)
Written in	Java
Operating system	Cross-platform
Type	Integration framework
License	Apache License 2.0
Website	camel.apache.org
Repository	github.com/apache/camel

Apache Camel is an open-source integration framework developed by the Apache Software Foundation. It provides a rule-based routing and mediation engine that implements the Enterprise Integration Patterns (EIPs) described by Gregor Hohpe and Bobby Woolf. Camel allows developers to define message routing and transformation rules using a variety of domain-specific languages (DSLs) including Java, XML, and YAML.

The framework ships over 300 built-in components for connecting to external systems including Kafka, JMS, REST APIs, SOAP, databases (JDBC), file systems (FTP, SFTP), cloud services (AWS, Azure, Google Cloud), and enterprise applications such as SAP and Salesforce.

Camel can run standalone, embedded in an application server, or on Kubernetes via Quarkus or Spring Boot.

History

The Apache Camel project was created by James Strachan and made its first commit on March 19, 2007. Version 1.0 was released on June 27, 2007. The project drew on ideas from the Enterprise Integration Patterns book and was influenced by earlier integration projects including Apache ServiceMix and Apache ActiveMQ.

In 2010, FuseSource was founded as a commercial company focused on Apache Camel, ActiveMQ, and ServiceMix. FuseSource was acquired by Progress Software in 2011 and subsequently by Red Hat in 2012. Red Hat productized Apache Camel as Red Hat Fuse (later renamed to Red Hat build of Apache Camel), providing commercial support and enterprise distribution.

In 2018, the Apache Camel K subproject was created to run Camel integrations natively on Kubernetes using a dedicated operator. In 2019, Camel Quarkus was introduced to bring Camel to the Quarkus runtime with ahead-of-time compilation support.

As of 2026, the project supports Model Context Protocol (MCP) for AI agent tool connectivity and A2A for inter-agent communication, positioning Camel as an integration runtime for AI agent architectures.

Architecture

Apache Camel's architecture is based on the concept of routes — sequences of processing steps that move messages from a source (consumer) to a destination (producer). Routes are defined using one of several DSLs (Java, XML, YAML) and can apply Enterprise Integration Patterns such as content-based router, message filter, aggregator, splitter, and dead letter channel.

Each external system is accessed through a component, which provides a URI-based endpoint for sending or receiving messages. With over 300 components, Camel supports a wide range of protocols and APIs without requiring custom adapter code.

The framework is modular — applications include only the components they need, keeping the runtime lightweight. A minimal Camel application can start in under one second when using Quarkus native compilation.

Community and development

Apache Camel is one of the larger projects at the Apache Software Foundation by commit volume. The project's git repository contains approximately 100,000 commits from over 1,600 contributors, with corporate email domains from over 450 distinct organizations appearing in the commit history. The Stack Overflow tag apache-camel has over 11,700 questions.

The project maintains multiple long-term support (LTS) release lines simultaneously and publishes migration guides for major version upgrades.

Adoption

Apache Camel is used in production across a range of industries. Several commercial integration platforms use Camel as their underlying runtime engine, including SAP Integration Suite and Huawei Cloud ROMA.

Notable publicly documented deployments include:

• CERN uses Apache Camel and Apache ActiveMQ for the Large Hadron Collider's control, monitoring, and alarm systems, processing 190 million messages per day across 85,000 machines.
• UPS processes tens of billions of messages per day on Apache Camel, the largest known deployment by message volume.
• The US Federal Aviation Administration (FAA) uses Camel for the System Wide Information Management (SWIM) program, providing real-time aviation weather, flight, and surveillance data sharing across the National Airspace System.
• IndiGo (India's largest airline) uses Camel to integrate over 400 applications, saving ₹500 million per year in fuel costs.
• Vodafone's Global Integration Gateway migrated from IBM DataPower to Apache Camel, integrating over 100 systems at 10,000+ transactions per second.
• Tata Motors uses Camel for dealer integration across 1,000+ dealerships, increasing API-driven transactions from 20% to 95%.

Ecosystem

The Apache Camel ecosystem includes several related projects:

• Apache Camel K — a Kubernetes operator for running Camel integrations natively on Kubernetes and OpenShift
• Apache Camel Quarkus — extensions for running Camel on the Quarkus runtime
• Apache Camel Spring Boot — integration with Spring Boot
• Kaoto — a visual designer for creating Camel routes
• Apache Camel Kamelets — pre-built, reusable connector templates

Books

• Ibsen, Claus; Anstey, Jonathan (2018). Camel in Action (2nd ed.). Manning Publications. ISBN 978-1617292934.
• Durai, Vignesh (2024). Apache Camel Cookbook. O'Reilly.

See also

• Enterprise Integration Patterns
• Enterprise service bus
• Message-oriented middleware
• Spring Integration
• MuleSoft
• Model Context Protocol

External links

• Official website

1. 1. Citation count: 14 third-party references

| # | Source | Type | |---|---|---| | 1 | Enterprise Integration Patterns (book) | Book | | 2 | InfoQ — Growing EAI with Apache Camel | Tech press | | 3 | DZone — Top Twelve Integration Patterns | Tech press | | 4 | InfoQ — Orchestrating AI Pipelines with Camel | Tech press | | 5 | GitHub — First commit | Primary source | | 6 | Red Hat — Fuse product page | Vendor (for history) | | 7 | OpenHub — Project stats | Third-party analytics | | 8 | Stack Overflow — Tag count | Third-party community | | 9 | SAP — Camel 3.14 upgrade notice | Third-party vendor | | 10 | Huawei Cloud ROMA | Third-party vendor | | 11 | Computerworld — CERN messaging | Third-party press | | 12 | YouTube — UPS presentation | Primary source | | 13 | CamelOne 2011 — FAA | Conference record | | 14 | Red Hat — IndiGo, Vodafone, Tata Motors | Case studies |

1. 1. Key differences from current article

| Current | Proposed | |---|---| | 2 references | 14 references | | No history | Full history (2007–2026) | | No adoption section | 6 named deployments with citations | | No community stats | 100K commits, 1,600+ contributors, 450+ companies, 11,700+ SO questions | | No ecosystem section | Camel K, Quarkus, Spring Boot, Kaoto, Kamelets | | Stub tag | Should qualify for stub removal | | No mention of AI/MCP | Current 2026 capabilities included | | "See also" lists dead projects (Petals ESB) | Updated to relevant projects | DavsClaus (talk) 21:56, 4 June 2026 (UTC)