←back to thread

Stop syncing everything

(sqlsync.dev)
656 points neilk | 1 comments | 31 Mar 25 17:07 UTC | HN request time: 0.282s | source
Show context
conradev ◴[02 Apr 25 02:19 UTC] No.43553127[source]▶
> After a client pulls a graft, it knows exactly what’s changed. It can use that information to determine precisely which pages are still valid and which pages need to be fetched

Curious how this compares to Cloud-Backed SQLite’s manifest: https://sqlite.org/cloudsqlite/doc/trunk/www/index.wiki

It’s similar to your design (sending changed pages), but doesn’t need any compute on the server, which I think is a huge win.

replies(2): >>43553571 #>>43553703 #
1. hamandcheese ◴[02 Apr 25 04:04 UTC] No.43553571[source]▶
Woah, hadn't seen this before but this is really cool!

I was recently looking for a way to do low scale serverless db in gcloud, this might be better than any of their actual offerings.

Cloud firestore seems like the obvious choice, but I couldn't figure out a way to make it work with existing gcloud credentials that are ubiquitous in our dev and CI environments. Maybe a skill issue.