Camel component for the LMAX disruptor
This component is still under heavy development, but the goal is to provide a component that is functionally comparable to the standard Camel SEDA component but based on a higher performance Disruptor instead of a standard blocking queue.
- Documentation
- Reconfiguring the usage of a Disruptor endpoint at runtime (e.g. adding/removing producers or consumers) is not very efficient
- Data sent over a Disruptor is directly processed and 'gone' if there is at least one consumer, late joiners only get new exchanges published after they've joined.