←back to thread

Stop syncing everything

(sqlsync.dev)
656 points neilk | 1 comments | 31 Mar 25 17:07 UTC | HN request time: 0.249s | source
Show context
mhahn ◴[02 Apr 25 04:28 UTC] No.43553675[source]▶
I looked at using turso embedded replicas for a realtime collaboration project and one downside was that each sync operation was fairly expensive. The minimum payload size is 4KB IIRC because it needs to sync the sqlite frame. Then they charge based on the number of sync operations so it wasn't a good fit for this particular use case.

I'm curious if the graft solution helps with this. The idea of just being able to ship a sqlite db to a mobile client that you can also mutate from a server is really powerful. I ended up basically building my own syncing engine to sync changes between clients and servers.

replies(1): >>43553723 #
1. carlsverre ◴[02 Apr 25 04:38 UTC] No.43553723[source]▶
For now, Graft suffers from the same minimum payload size of 4KB. However, there are ways to eliminate that. I've filed an issue to resolve this in Graft (https://github.com/orbitinghail/graft/issues/35), thanks for the reminder!

As for the more general question though, by shipping pages you will often ship more data than the equivalent logical replication approach. This is a tradeoff you make for a much simpler approach to strong consistency on top of arbitrary data models.

I'd love to learn more about the approach you took with your sync engine! It's so fun how much energy is in the replication space right now!