The LMAX Architecture - 100K TPS at Less than 1ms Latency

Re:The LMAX Architecture - 100K TPS at Less than 1ms Latency by koevet on Sunday October 30, 2011 @07:00AM (#3174084)

The Disruptor components are not part of a single threaded process, as far as I understand

"Also these three tasks are relatively independent, all of them need to be done before the Business Logic Processor works on a message, but they can done in any order. So unlike with the Business Logic Processor, where each trade changes the market for subsequent trades, there is a natural fit for concurrency."

I think that the Disruptor can run on the save JVM as the business logic, also to avoid remoting-related bottlenecks.

[ Parent | on HN ]

Re:The LMAX Architecture - 100K TPS at Less than 1ms Latency by aaronblohowiak on Sunday October 30, 2011 @09:46AM (#3174354)

The BLP is single-threaded, and the component that modifies the application's current state. It is my understanding that "Events" in event-sourcing are immutable and that state is just a memoized computation over the total journal of events -- so the layer of atomiticity that is provided is at the event level (as the BLP only processes one event at a time.)

[ Parent | on HN ]

Re:The LMAX Architecture - 100K TPS at Less than 1ms Latency by jacques_chester on Sunday October 30, 2011 @11:41AM (#3174603)

So the system is as "weak as its strongest link".

Hmm.

[ Parent | on HN ]

Re:The LMAX Architecture - 100K TPS at Less than 1ms Latency by _grrr on Sunday October 30, 2011 @07:25AM (#3174109)

The hand off between producer and consumer can be configured to be both synchronous (single threaded) as well as asynchronous (one producer thread, many consumers threads).

[ Parent | on HN ]