Migration from Red Hat Fuse to the Red Hat build of Apache Camel

An integration framework available as part of Red Hat Application Foundations, Red Hat Integration, and Developer Sandbox.

Try the Developer Sandbox
Overview Getting started Migrate from Red Hat Fuse
  1. Home
  2. Products
  3. Overview
  4. Migrate from Red Hat Fuse

Migrate from Red Hat Fuse 7 to the Red Hat build of Apache Camel

Red Hat® Fuse 7 reached end-of-life on June 30, 2024, and is now only supported through extended life cycle support. Customers and developers running applications on Red Hat Fuse 7 should migrate to the Red Hat build of Apache Camel—part of Red Hat Application Foundations.

camel logo

Choose your Camel runtime

Apache Camel is the most popular open source integration framework today. The Red Hat build of Apache Camel targets modern cloud-native and microservices-based application runtimes such as Spring Boot and Quarkus, which are perfect for developers planning a large number of services on Kubernetes. Camel-based integrations on all-in-one application server architectures like OSGi (Karaf) or Java Enterprise Edition (JBoss EAP) are no longer supported.

Camel and Spring Boot form a very popular combo for developers planning for a large number of services deployed on Kubernetes. The movement to microservices and distributed architectures has influenced integration teams to increasingly adopt smaller and more developer-friendly runtimes.

camel_spring_boot_icon

Quarkus is a Java framework tailored for deployment on Kubernetes. Camel on Quarkus is the latest Camel runtime generation. It allows you to run integration processes with super low memory usage, fast startup, and outstanding performance. Quarkus plays a crucial role in ensuring Java's continued relevance and saves organizations from investing effort to seek alternatives to Java. Quarkus also protects an organization’s investment in their Java codebase and preserves continuity.

camel_quarkus_icon
Choose the right runtime

Migration architecture

There are 2 migration paths to the Red Hat build of Apache Camel.

  1. Migrate to the Red Hat build of Apache Camel without adopting Red Hat OpenShift®. This path supports a standalone mode on virtual machines (VMs) or bare metal using Camel for Quarkus and Camel for Spring Boot runtimes.
  2. Migrate to the Red Hat build of Apache Camel by adopting Red Hat Openshift. This path supports a container-based application platform using Camel for Quarkus and Camel for Spring Boot runtimes.
2025_camel graphic

Migration instructions and considerations

choosing_a_dsl_icon

Choosing a DSL

Every developer will have to choose a domain specific language (DSL) to connect subsystems, storage, message brokers, and more.
solution_pattern_icon

Solution pattern

This solution pattern can help visualize the migration from Red Hat Fuse to the Red Hat build of Apache Camel—featuring pre-configured, ready-to-use migration templates tailored for the Quarkus and Spring Boot runtimes.
migration_instructions_icon

Migration instructions

Consult the respective migration guides for Red Hat build of Apache Camel for Quarkus and Red Hat build of Apache Camel for Spring Boot.
tooling_icon

Tooling

A tooling guide discusses various Visual Studio Code extensions and Camel JBang, and the Red Hat build includes a Hawtio diagnostic console.
apache_camel_learning icon

Learning resources

Review use cases and hands-on trials in the Developer Sandbox or learn to create and deploy a Camel integration as a serverless service.
professional_services_help_icon

Professional help

Contact Red Hat to discuss ways we can ease your migration.