8 ms·
In my experience multi-writer is because of latency or HADR stuff - have all your data in all regions at the same time, but the method (via the tlog) seems like
by hobs 1y ago
In my experience multi-writer is because of latency or HADR stuff - have all your data in all regions at the same time, but the method (via the tlog) seems like it sort of defeats what those sorts of systems might be able to historically do (write multiple places from the app at the same time so as to have the lowest possible chance of data loss.)
- shermantanktop 1y agoYes, I call it spoke-and-hub. The sharded spokes accept the writes and replicate back to the hub, where all shards coexist. Useful for metric ingestion. Not useful for bank ledgers or whatever.
- hobs 1y agoYeah, some instances also have all the shards maintain all the state and just accept writes in your partition of values, merge replication in sql server works like this.