Comment by akoboldfrying
4 days ago
If you use hashes of the content itself for your UUIDs, you'll (a) get deduplication and data consistency checking for free and (b) have basically implemented (a subset of) git that uses S3 backing instead of a local filesystem directory :)
for smallish databases, where uuid is surogate id, i would trust dbos/postgres replication. replication is just too hard to role your own.
tangentially, for dbs with large blobs, lot's of easy tricks when uuids are immutable digests.
syncing, say, two blob stores, A and B, boils down to jaccard metric, as a first order approximation
diffing the two digest sets at point in time is second order approximation.
and don't forget logical replication ...