// Do not edit directly!
// This file was generated by camel-quarkus-maven-plugin:update-extension-doc-page
= Disruptor
:cq-artifact-id: camel-quarkus-disruptor
:cq-native-supported: true
:cq-status: Stable
:cq-description: Provides asynchronous SEDA behavior using LMAX Disruptor.
:cq-deprecated: false
:cq-jvm-since: 1.1.0
:cq-native-since: 1.2.0

[.badges]
[.badge-key]##JVM since##[.badge-supported]##1.1.0## [.badge-key]##Native since##[.badge-supported]##1.2.0##

Provides asynchronous SEDA behavior using LMAX Disruptor.

== What's inside

* xref:{cq-camel-components}::disruptor-component.adoc[Disruptor component], URI syntax: `disruptor:name`
* xref:{cq-camel-components}::disruptor-component.adoc[Disruptor VM component], URI syntax: `disruptor-vm:name`

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

== Maven coordinates

[source,xml]
----
<dependency>
    <groupId>org.apache.camel.quarkus</groupId>
    <artifactId>camel-quarkus-disruptor</artifactId>
</dependency>
----

Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.

== Camel Quarkus limitations

The `disruptor-vm` component is not available on Camel Quarkus. This is because it is supposed to provide support for communication across multiple CamelContext instances within a single JVM, but by design, there is always just a single `CamelContext` on Camel Quarkus. Therefore `disruptor-vm` would make no sense.

