[the_precipitate]

Yeah, and this doesn't seems to be that useful. At least I don't understand why one should do this on a strong ACID relational database.

[hobs]

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]

Yes, 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.