Thanks for this. I love the idea of breaking up a flow into separately scheduled but still linear message flow. I wrote about a similar idea in ideas2 https:

Thanks for this. I love the idea of breaking up a flow into separately scheduled but still linear message flow. I wrote about a similar idea in ideas2 https://github.com/samsquire/ideas2#84-communication-code-slices https://github.com/samsquire/ideas2#84-communication-code-sl... The idea is that I enrich my code with comments and a transpiler schedules different parts of the code to different machines and inserts communication between blocks. I read about how Zookeeper algorithm for transactionality and robustness to messages being dropped, which is interesting reading. https://zookeeper.apache.org/doc/r3.4.13/zookeeperInternals.html https://zookeeper.apache.org/doc/r3.4.13/zookeeperInternals.... How does Mats compare? LMAX disruptor has a pattern where you split up each side of an IO request into two events, to avoid blocking in an handler. So you would always insert a new event to handle an IO response.