Chapter 3. Camel Quarkus release notes

Camel Quarkus is available as a Technology Preview component in Red Hat Integration 2021.Q2.


In this Technology Preview, Camel Quarkus is supported in JVM mode only.

Camel Quarkus brings the integration capabilities of Apache Camel and its vast component library to the Quarkus runtime. By using Camel Quarkus, you can to take advantage of the performance benefits, developer joy and the container first ethos which Quarkus provides.

Camel Quarkus provides Quarkus extensions which are units of the Quarkus distribution. Extensions configure, boot and integrate Camel components in your Quarkus application and are typically configured as dependencies in your project.

Camel Quarkus takes advantage of the many performance improvements made in Camel 3, which results in a lower memory footprint, less reliance on reflection and faster startup times.


Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend implementing any Technology Preview features in production environments.

This Technology Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about support scope, see Technology Preview Features Support Scope.

3.1. Camel Quarkus features

The Camel Quarkus Technology Preview provides the following main features:

3.1.1. Platform and core component versions

  • OpenShift Container Platform 4.6
  • Quarkus 1.11 Java runtime
  • Apache Camel 3.7
  • Apache Camel Quarkus 1.6
  • OpenJDK 11

3.1.2. Technology Preview features

Fast startup and low RSS memory
Using the optimized build-time and ahead-of-time (AOT) compilation features of Quarkus, your Camel application can be pre-configured at build time resulting in fast startup times.
Highly configurable

All of the important aspects of a Camel Quarkus application can be set up programatically with CDI (Contexts and Dependency Injection) or via configuration properties. By default, a CamelContext is configured and automatically started for you.

Check out the Configuring your Quarkus applications guide for more information on the different ways to bootstrap and configure an application.

Integrates with existing Quarkus extensions
Quarkus provides extensions for libraries and frameworks that are used by some Camel components which inherit native support and configuration options.

3.1.3. Available Camel Quarkus extensions in Technology Preview

  • camel-quarkus-main
  • camel-quarkus-timer
  • camel-quarkus-log
  • camel-quarkus-file
  • camel-quarkus-ftp
  • camel-quarkus-direct
  • camel-quarkus-bean
  • camel-quarkus-mock
  • camel-quarkus-bindy
  • camel-quarkus-seda
  • camel-quarkus-core
  • camel-quarkus-microprofile-health