←back to thread

Stop syncing everything

(sqlsync.dev)
642 points neilk | 1 comments | 31 Mar 25 17:07 UTC | HN request time: 0.219s | source
Show context
theSherwood ◴[02 Apr 25 08:17 UTC] No.43554626[source]▶
This is a very interesting approach. Using pages as the basic sync unit seems to simplify a lot. It also makes the sync of arbitrary bytes possible. But it does seem that if your sync is this coarse-grained that there would be lots of conflicting writes in applications with a lot of concurrent users (even if they are updating semantically unrelated data). Seems like OT or CRDT would be better in such a use-case. I'd be interested to see some real-world benchmarks to see how contention scales with the number of users.
replies(1): >>43557368 #
1. carlsverre ◴[02 Apr 25 14:52 UTC] No.43557368[source]▶
Thank you! You're 1000% correct, Graft's approach is not a good fit for high write contention on a single Volume. Graft instead is designed for architectures that can either partition writes[^1] or can represent writes as bundled mutations and apply them in a single location that can enforce order (the SQLSync model).

Basically, Graft is not the full story, but as you point out - because it's so simple it's easy to build different solutions on top of it.

[^1]: either across Volumes or across pages, Graft can handle automatically merging non-overlapping page sets