←back to thread

Stop syncing everything

(sqlsync.dev)
637 points neilk | 1 comments | 31 Mar 25 17:07 UTC | HN request time: 0.209s | source
Show context
londons_explore ◴[02 Apr 25 07:32 UTC] No.43554435[source]▶
This approach has a problem when the mobile client is on the end of a very slow connection, yet the diff that needs to be synced is gigabytes, perhaps because it's an initial sync or the database got bloated for whatever reason.

A hybrid approach is to detect slow syncing (for example when sync hasn't completed after 5 seconds), and instead send queries directly to the server because there is a good chance the task the user wants to complete doesn't depend on the bloated records.

replies(1): >>43556300 #
1. carlsverre ◴[02 Apr 25 13:12 UTC] No.43556300[source]▶
This is a great point. Solutions like Graft which involve syncing data to the edge work poorly when the dataset size is too large and not partitioned enough to be consistency partial.

This is why Graft isn't just focused on client sync. By expanding the focus to serverless functions and the edge, Graft is able to run the exact same workload on the exact same snapshot (which it can validate trivially due to its consistency guarantees) anywhere. This means that a client's workload can be trivially moved to the edge where there may be more resources, a better network connection, or existing cached state.