Disruptor with handlers doing async activities

[Manish Deliwala]

Hello, 

Has anyone uses lmax disruptor in the context where the async flow based on Future or Observable needs to be used as part of the DSL? Once someone shows interest, i will add more details. Essentially what we find is (obviously), lmax fits the in-jvm capability where throughput and latency are quite good.  Anytime we venture into out-of-jvm via reactive framework such as vert.x or reactive - there is no way to manage the callback flow through LMAX.

[Michael Barker]

Hi Manish,

I believe that at one point the project reactor team were looking at a reactive streams implementation on top of the Disruptor.  I'm not sure how far that has moved forward.  Apart from that, I don't know of any future or observable APIs on top of the Disruptor.

If you are looking for out-of-jvm frameworks for async message passing, you should look at Aeron.  It has IPC and UDP (unicast/multicast) channels for communicating between processes.

Mike.

On 9 May 2017 at 11:40, Manish Deliwala <ond...@gmail.com> wrote:

Hello, 

Has anyone uses lmax disruptor in the context where the async flow based on Future or Observable needs to be used as part of the DSL? Once someone shows interest, i will add more details. Essentially what we find is (obviously), lmax fits the in-jvm capability where throughput and latency are quite good.  Anytime we venture into out-of-jvm via reactive framework such as vert.x or reactive - there is no way to manage the callback flow through LMAX.

--
You received this message because you are subscribed to the Google Groups "Disruptor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lmax-disruptor+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.