It's weird to me what a splash this had at the time. I'm kind of forgetting what the essential adds are versus existing ring buffer systems?<p>Iirc mainly it's that rather than there being a producer/consumer role, there can be multiple work stages? An item might need to be extracted, transformed, and loaded, and item can stay in the queue while waiting for each stage before being done? This is how they get the dependency graph? Are there other major innovations here? <a href="https://lmax-exchange.github.io/disruptor/disruptor.html#_dependency_graphs" rel="nofollow">https://lmax-exchange.github.io/disruptor/disruptor.html#_de...</a><p>Recently notable, io_uring also has submission/completion queues which are also ring buffers. Since the submission & completion won't necessarily be in order, since any given work item could take wildly different times, a lmax style item wouldn't make sense; each ring buffer wants to be short lived in this impl.