[CAMEL-9692] LMAX Disruptor Component: Make it compatible with async routing engine

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.16.2
• Fix Version/s: Future
• Component/s: camel-disruptor
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Raúl Kripalani
• Created: 10/Mar/16 09:24
• Updated: 02/Sep/22 09:16
• Resolved: 02/Sep/22 09:16

Description

Currently, the camel-disruptor component is not compatible with the async routing engine.

Therefore, in an InOut scenario, it keeps the calling thread waiting until the CountDownLatch fires.

This degree of synchronicity is contrary to a message-oriented middleware and contrary to the philosophy of the LMAX Disruptor itself.

We should strive to make it fully async via an AsyncCallback.

According to https://stackoverflow.com/questions/6559308/how-does-lmaxs-disruptor-pattern-work, it should be natively possible:

We also allow consumers to wait on the results of other consumers without having to put another queuing stage between them. A consumer can simply watch the sequence number of a consumer that it is dependent on. This avoids the need for join stages in pipeline.