There's a whole database, Datomic, that works roughly this way -- not the UDP multicast but the idea of having a slightly more nuanced consistency/availability/partition tolerance tradeoff by having a thin transaction organizer which is not partition tolerant and officially states which one came first and second, upstream of the replicas that grant normal availability.<p>I would have liked the discussion about Raft/Paxos that they said they'd leave out of this episode though :(
If you're interested in this topic, I highly suggest some of the talks and papers about the LMAX Disruptor [0] and Martin Thompson's latest project Aeron [1]. It targets the JVM, but the lessons are generally applicable since I don't think Concord/Aria are open source.<p>[0] <a href="https://lmax-exchange.github.io/disruptor/" rel="nofollow">https://lmax-exchange.github.io/disruptor/</a>
[1] <a href="https://github.com/real-logic/aeron" rel="nofollow">https://github.com/real-logic/aeron</a>
This is somewhat interesting but note they start by saying they use the word "state machine" not in fact to refer to a state machine, but rather something more like a closure or class instance (they weren't really clear).
Blockchain is also an example of SMR with less assumptions: ip addresses and public keys unknown upfront (permissionless), asynchronous model, and byzantine actors.
This was an interesting episode. However, I thought this pattern was called actors. Did anyone else get that sense? I have never heard that called a state machine.
This is the only "podcast" I've bothered to actually "listen" to (I read the transcripts). Each episode is very informative often about several subjects.