Best read strategy for a disruptor

[Noah Cornwell]

Hi All,

The typical use case for a disruptor is events in -> business logic -> events out. My use case is slightly different, events in -> update state | read state when requested. What are the typical strategies that people use here? Disruptor proxy looks interesting (https://github.com/LMAX-Exchange/disruptor-proxy) or something similar.

If you've got some sort of front end like a website how would you present data to a user?

Best,

Noah

[Michael Barker]

Typically for handling async responses back to a web application we've used Async Servlets (part of 3.0 spec) and Web Sockets.

Mike.

--
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.