[gawi]

This is very interesting. I have no doubts that not having to deal with fault tolerance at the application level compensates for the efforts to put in place this architecture. And yes, in my opinion, "application-level consensus" is the perfect term to designate this architecture.

[mr_luc]

I agree. One place where application-level consensus is fairly common is in Elixir applications, mostly thanks to the crdt implementation that's nicely wrapped up by Phoenix.Tracker in the phoenix_pubsub library.

This is used by the Phoenix project's Presence module to provide a distributed notion of what users are 'present', but it's also used by others to do service location using hash rings, or implement a dht, etc. I've used it for master election and failover on a few projects for little services.