4 ms·
Is the idea that you'll check replication status after making each write? Or I guess you could do this at the application level, like after completing a transac
by foota 2y ago
Is the idea that you'll check replication status after making each write? Or I guess you could do this at the application level, like after completing a transaction to e.g., sqlite check that there's at least one other zone caught up before acking whatever call the user made?
- leg 2y agoMany enterprise storage systems have the durability/availability tradeoff like these replicated disks when replicating outside of a single datacenter. (Oracle calls it "max availability": try to synchronously replicate, but if the remote side is offline, allow transactions to commit.) Real world banks run on these sorts of systems. Users don't continuously check replication status. They rely on it being synchronous almost all the time. 3 way quorum replication is great, but you then need to send to more data centers, potentially affecting performance. There's a tradeoff. (I work on GCP storage)