Getting Started with Apache Camel and Spring Boot

Getting Started with Apache Camel and Spring Boot

Table Of Contents

Apache Camel is an integration framework with a programming model for integrating a wide variety of applications.

It is also a good fit for microservice architectures where we need to communicate between different microservices and other upstream and downstream systems like databases and messaging systems.

In this article, we will look at using Apache Camel for building integration logic in microservice applications built with Spring Boot with the help of code examples.

Example Code

This article is accompanied by a working code example on GitHub.

What is Apache Camel

As explained at the start, Apache Camel is an integration framework. Camel can do :

  1. Routing: Take a data payload also called “message” from a source system to a destination system
  2. Mediation: Message processing like filtering the message based on one or more message attributes, modifying certain fields of the message, enrichment by making API calls, etc.

Some of the important concepts of Apache Camel used during integration are shown in this diagram:

Camel Message Flow

Let us get a basic understanding of these concepts before proceeding further.

Camel Context

Camel context is the runtime container of all the Camel constructs and executes the routing rules. The Camel context activates the routing rules at startup by loading all the resources required for their execution.

The Camel context is described by the CamelContext interface and is autoconfigured by default if running in a Spring container.

Routes and Endpoints

A Route is the most basic construct which we use to define the path a message should take while moving from source to destination. We define routes using a Domain Specific Language (DSL).

Routes are loaded in the Camel context and are used to execute the routing logic when the route is triggered. Each route is identified by a unique identifier in the Camel context.

Endpoints represent the source and destination of a message. They are usually referred to in the Domain Specific Language (DSL) via their URIs. Examples of an endpoint can be a URL of a web application or source or destination of a messaging system.

Domain Specific Language (DSL)

We define routes in Apache Camel with a variety of Domain Specific Languages (DSL). The Java DSL and the Spring XML DSL are the two main types of DSLs used in Spring applications.

Here is an example of a route defined in Java DSL using the RouteBuilder class:

    RouteBuilder builder = new RouteBuilder() {

      public void configure() throws Exception {
        // Route definition in Java DSL for 
        // moving file from jms queue to file system.

Here we have defined a route with a JMS queue as a source and a file endpoint as a destination by using the RouteBuilder class. The RouteBuilder class creates routing rules using the DSL. Instances of RouteBuilder class are added to the Camel context.

The same route defined using Spring XML DSL looks like this :

<beans xmlns=""
       xsi:schemaLocation="" >

  <camelContext id="sendtoqueue" 
      <from uri="jms:queue:myQueue"/>
      <to uri="file://mysrc"/>



The transport of a message from the source to the destination goes through multiple steps. Processing in each step might require connecting to different types of resources in the message flow like an invocation of a bean method or calling an API. We use components to perform the function of connecting to these resources.

For example, the route defined with the RouteBuilder class in Java DSL uses the file component to bridge to the file system and the jms component to bridge to the JMS provider.

    RouteBuilder builder = new RouteBuilder() {

      public void configure() throws Exception {
        // Route definition in Java DSL for 
        // moving file from jms queue to file system.

Camel has several pre-built components and many others built by communities. Here is a snippet of the components available in Camel which gives us an idea of the wide range of systems we can integrate using the framework:

  • ActiveMQ
  • AMQP
  • Async HTTP Client
  • Atom
  • Avro RPC
  • AWS2 DynamoDB
  • AWS2 Lambda
  • AWS2 SQS
  • AWS2 SNS
  • Azure CosmosDB
  • Azure Storage Blob
  • Azure Storage Queue
  • Bean
  • Cassandra CQL
  • Consul
  • CouchDB
  • Cron
  • Direct
  • Docker
  • Elasticsearch
  • Facebook
  • FTP
  • Google Cloud Storage
  • Google Cloud Function
  • GraphQL
  • Google Pubsub
  • gRPC
  • HTTP

These functions are grouped in separate Jar files. Depending on the component we are using, we need to include the corresponding Jar dependency.

For our example, we need to include the camel-jms dependency and use the component by referring to the documentation of Camel JMS component.

We can also build our own components by implementing the Component interface.

Using Apache Camel in Spring Boot

Camel support for Spring Boot includes an opinionated auto-configuration of the Camel context and starters for many Camel components. The auto-configuration of the Camel context detects Camel routes available in the Spring context and registers the key Camel utilities (like producer template, consumer template, and the type converter) as Spring beans.

Let us understand this with the help of an example. We will set up a simple route for calling a bean method and invoke that route from a REST endpoint.

Let us first create a Spring Boot project with the help of the Spring boot Initializr, and then open the project in our favorite IDE.

Adding the Dependencies

Apache Camel ships a Spring Boot Starter module camel-spring-boot-starter that allows us to use Camel in Spring Boot applications.

Let us first add the Camel Spring Boot BOM to our Maven pom.xml :


    <!-- Camel BOM -->
    <!-- ... other BOMs or dependencies ... -->


The camel-spring-boot-bom contains all the Camel Spring Boot starter JAR files.

Next, let us add the Camel Spring Boot starter:


Adding the camel-spring-boot-starter sets up the Camel Context.

We need to further add the starters for the components required by our Spring Boot application :


Here we have added three dependencies with the starters for using the components for servlet, jackson, and swagger which will perform the following functions:

  1. The servlet component will provide HTTP based endpoints for consuming HTTP requests arriving at an HTTP endpoint bound to a published Servlet.
  2. The jackson component will be used for marshaling and unmarshalling between JavaScript Object Notation (JSON) and object representations.
  3. The swagger component will expose the REST services and their APIs using Swagger/Open API specification.

Defining a Route with Java DSL’s RouteBuilder

Let us now create a route for fetching products by using a Spring bean method. We create Camel routes by extending the RouteBuilder class and overriding its configure method to define our routing rules in Java Domain Specific Language (DSL).

Each of the router classes is instantiated once and is registered with the CamelContext object.

Our class containing the routing rule defined using Java Domain Specific Language (DSL) looks like this:

public class FetchProductsRoute extends RouteBuilder {

  public void configure() throws Exception {
      .log(">>> ${body}")
      .bean(ProductService.class, "fetchProductsByCategory")


Here we are creating the route by defining the Java DSL in a class FetchProductsRoute by extending RouteBuilder class. We defined the endpoint as direct:fetchProducts and provided a route identifier direct-fetchProducts. The prefix direct: in the name of the endpoint makes it possible to call the route from another Camel route using the direct Camel component.

Triggering a Route with Templates

We can invoke the routes with ProducerTemplate and ConsumerTemplate. The ProducerTemplate is used as an easy way of sending messages to a Camel endpoint.

Both of these templates are similar to the template utility classes in the Spring Framework like JmsTemplate or JdbcTemplate that simplify access to the JMS and JDBC APIs.

Let us invoke the route we created earlier from a resource class in our application :

public class ProductResource {
  private ProducerTemplate producerTemplate;
  public List<Product> getProductsByCategory(
                @PathVariable("category") final String category){
    List<Product> products = producerTemplate
       .requestBody("direct:fetchProducts", category, List.class);
    return products;

public class AppConfig {
  private  CamelContext camelContext;
  ProducerTemplate producerTemplate() {
    return camelContext.createProducerTemplate();
  ConsumerTemplate consumerTemplate() {
    return camelContext.createConsumerTemplate();


Here we have defined a REST endpoint in our resource class with a GET method for fetching products by category. We are invoking our Camel route inside the method by using the producerTemplate which we configured in our Spring configuration.

In our Spring configuration we have defined the producerTemplate and consumerTemplate by calling corresponding methods on the CamelContext which is available in the ApplicationContext.

Defining a Route with Splitter-Aggregator Enterprise Integration Pattern

Let us now look at a route where we will use an Enterprise Integration Pattern.

Camel provides implementations for many of the Enterprise Integration Patterns from the book by Gregor Hohpe and Bobby Woolf. We will use the Splitter and Aggregator integration patterns in our example.

We can split a single message into multiple fragments with the Splitter and process them individually. After that, we can use the Aggregator to combine those individual fragments into a single message.

Selecting the Enterprise Integration Pattern (EIP)

Before trying to build our integration logic, we should look for the integration pattern most appropriate for fulfilling our use case.

Let us see an example of defining a route with the Splitter and Aggregate integration patterns. Here we will consider a hypothetical scenario of building a REST API for an E-Commerce application for processing an order placed by a customer. We will expect our order processing API to perform the following steps:

  1. Fetch the list of items from the shopping cart
  2. Fetch the price of each order line item in the cart
  3. Calculate the sum of prices of all order line items to generate the order invoice.

After finishing step 1, we want to fetch the price of each order line item in step 2. We want to fetch them in parallel since they are not dependent on each other. There are multiple ways of doing this kind of processing.

However, since design patterns are accepted solutions to recurring problems within a given context, we will search for a pattern closely resembling our problem from our list of Enterprise Integration Patterns. After looking through the list, we find that the Splitter and Aggregator patterns are best suited to do this processing.

Applying the Enterprise Integration Pattern (EIP)

Next, we will refer to Apache Camel’s documentation to learn about the usage of the Splitter and Aggregator integration patterns to build our routes.

Let us apply these patterns by performing the below steps:

  1. Fetch the order lines from the shopping cart and then split them into individual order line items with the Splitter EIP.
  2. For each order line item, fetch the price, apply discounts, etc. These steps are running in parallel.
  3. Aggregate price from each line item in PriceAggregationStrategy class which implements AggregationStrategy interface.

Our route for using this Enterprise Integration Pattern (EIP) looks like this:

public class OrderProcessingRoute extends RouteBuilder {
  private PriceAggregationStrategy priceAggregationStrategy;

  public void configure() throws Exception {
    .split(body(), priceAggregationStrategy).parallelProcessing()

public class PriceAggregationStrategy implements AggregationStrategy{
  public Exchange aggregate(Exchange oldExchange, Exchange newExchange) {
    OrderLine newBody = newExchange.getIn().getBody(OrderLine.class);
        if (oldExchange == null) {
            Order order = new Order();
            newExchange.getIn().setBody(order, Order.class);
            return newExchange;
        OrderLine newOrderLine = newExchange.getIn()
        Order order = oldExchange.getIn().getBody(Order.class);
        order.setOrderPrice(order.getOrderPrice() + newOrderLine.getPrice());
        return oldExchange;


public class PricingService {
  public OrderLine calculatePrice(final OrderLine orderLine ) {
    String category = orderLine.getProduct().getProductCategory();
    return orderLine;


Here we have defined a route in Java DSL which splits the incoming message (collection of order lines) into individual order line items. Each order line item is sent to the calculatePrice method of the PricingService class to compute the price of the items.

Next, we have tied up an aggregator after the split step. The aggregator implements the AggregationStrategy interface and our aggregation logic is inside the overridden aggregate() method. In the aggregate() method, we take each of the order line items and consolidate them into a single order object.

Consuming the Route with Splitter Aggregator Pattern from REST Styled DSL

Let us next use the REST styled DSL in Apache Camel to define REST APIs with the HTTP verbs like GET, POST, PUT, and, DELETE. The actual REST transport is leveraged by using Camel REST components such as Netty HTTP, Servlet, and others that have native REST integration.

To use the Rest DSL in Java, we need to extend the RouteBuilder class and define the routes in the configure method similar to how we created regular Camel routes earlier.

Let us define a hypothetical REST service for processing orders by using the rest construct in the Java DSL to define the API. We will also generate a specification for the API based on the OpenAPI Specification (OAS):

public class RestApiRoute  extends RouteBuilder {
  private Environment env;

  public void configure() throws Exception {
        .apiProperty("api.title", "REST API for processing Order")
        .apiProperty("api.version", "1.0")
        .apiProperty("cors", "true")
        .port(env.getProperty("server.port", "8080"))
    .get("/process").description("Process order")
    .bean(OrderService.class, "generateOrder")

This defines a REST service of type GET with URL mappings /order/process.

We then route directly to the Camel endpoint of our route named direct:fetchProcess using the Splitter and Aggregator Enterprise Integration pattern that we created earlier using the to construct in the DSL.

When to Use and Not to Use Apache Camel

As we saw in our examples, we can easily accomplish the above tasks with custom coding instead of using Apache Camel. Let us understand some of the situations when we should consider using Apache Camel for our integration requirements:

  1. Apache Camel with a rich set of components will be useful in applications requiring integration with systems over different protocols (like files, APIs, or JMS Queues).
  2. Apache Camel’s implementation of Enterprise Integration Patterns is useful to fulfill complex integration requirements with tried and tested solutions for recurring integration scenarios.
  3. Orchestration and choreography in microservices can be defined with Domain Specific Language in Apache Camel routes. Routes help to keep the core business logic decoupled from the communication logic and satisfy one of the key Microservice principles of SRP (single responsibility principle).
  4. Apache Camel works very well with Java and Spring applications.
  5. Working with Java Objects (POJOs): Apache Camel is a Java framework, so it is especially good at working with Java objects. So if we are working with a file format like XML, JSON that can be de-serialized into a Java object then it will be handled easily by Camel.

On the contrary, we should avoid using Apache Camel in the following scenarios:

  1. If we have simple integration involving calling few APIs
  2. Camel is not known to perform well for heavy data processing
  3. Camel will also not be good for teams lacking in Java skills

Generally, the best use cases for Camel are where we have a source of data that we want to consume from like incoming messages on a queue, or fetching data from an API and a target, where we want to send the data to.


In this article, we looked at the important concepts of Apache Camel and used it to build integration logic in a Spring Boot application. Here is a summary of the things we covered:

  1. Apache Camel is an integration framework providing a programming model along with implementations of many Enterprise Integration Patterns.
  2. We use different types of Domain Specific Languages (DSL) to define the routing rules of the message.
  3. A Route is the most basic construct which we specify with a DSL to define the path a message should take while moving from source to destination.
  4. Camel context is the runtime container for executing Camel routes.
  5. We built a route with the Splitter and Aggregator Enterprise Integration Patterns and invoked it from a REST DSL to demonstrate solving integration problems by applying Enterprise Integration Patterns because patterns are accepted solutions to recurring problems within a given context.
  6. Finally we looked at some scenarios where using Apache Camel will benefit us.

I hope this post has given you a good introduction to Apache Camel and we can use Camel with Spring Boot applications. This should help you to get started with building applications using Spring with Apache Camel.

You can refer to all the source code used in the article on Github.

Written By:

Pratik Das

Written By:

Pratik Das

Software Engineer, Consultant and Architect with current expertise in Enterprise and Cloud Architecture, serverless technologies, Microservices, and Devops.

Recent Posts

Handling Timezones in a Spring Boot Application

It is common to encounter applications that run in different time zones. Handling date and time operations consistently across multiple layers of an application can be tricky.

Read more

JUnit 5 by Examples

In software development, unit testing means writing tests to verify that our code is working as logical units. Different people tend to think of a “logical unit” in different ways.

Read more

Scheduling Jobs with Node.js

Have you ever wanted to perform a specific task on your application server at specific times without physically running them yourself?

Read more