Congratulations on the release! > multi-region replicated database [..] once data is committed, it's durable [...] > strongly consistent on the server-side D

Congratulations on the release! > multi-region replicated database [..] once data is committed, it's durable [...] > strongly consistent on the server-side Do you mind elaborating a bit more here? Around perhaps what happens underneath the hood when failing over, etc. Do you have a single "co-ordinator" of sorts ensuring strict serializability, if so what do you do when failing this over? Or is it a quorum based approach like Paxos/Raft?