JVM since0.0.1 Native since0.0.1

Read and write from/to Infinispan distributed key/value store and data grid.

What’s inside

Please refer to the above link for usage and configuration details.

Maven coordinates

Or add the coordinates to your existing project:


Check the User guide for more information about writing Camel Quarkus applications.


Infinispan client configuration

You can configure Camel Infinispan in one of two ways.

More details about these two configuration methods is described below.

Camel Infinispan component and endpoint configuration

When using 'pure' Camel Infinispan component and endpoint configuration (I.e where’s there’s no quarkus.infinispan-client configuration set), you must disable generation of the default Quarkus Infinispan RemoteCacheManager bean by adding the following configuration to


If you wish to take advantage of Quarkus Dev Services for Infinispan, the Camel Infinispan component can be configured as follows in

# dev / test mode Quarkus Infinispan Dev services configuration

# Example prod mode configuration

Quarkus Infinispan configuration

When using the Quarkus Infinispan extension configuration properties, the Quarkus Infinispan extensions creates and manages a RemoteCacheManager bean.

The bean will get automatically autowired into the Camel Infinispan component on application startup.

Note that to materialize the RemoteCacheManager beans, you must add injection points for them. For example:

public class Routes extends RouteBuilder {
    // Injects the default unnamed RemoteCacheManager
    RemoteCacheManager cacheManager;

    // If configured, injects an optional named RemoteCacheManager
    RemoteCacheManager namedCacheManager;

    public void configure() {
        // Route configuration here...

Additional Camel Quarkus configuration

Camel Infinispan InfinispanRemoteAggregationRepository in native mode

If you chose to use the InfinispanRemoteAggregationRepository in native mode, then you must enable native serialization support.