Lessons learned from building a sync-engine and reactivity system with SQLite
1–10 of 41 posts
Re: Lessons learned from building a sync-engine and reactivity system with SQLite
#2very cool! have you tried Tanstack DB and ElectricSQL?
Re: Lessons learned from building a sync-engine and reactivity system with SQLite
#3very cool stuff!
Re: Lessons learned from building a sync-engine and reactivity system with SQLite
#4I love the timing of how, over the past week or so I've been digging into the ecosystem and options around this, and now here's another article!
Re: Lessons learned from building a sync-engine and reactivity system with SQLite
#5very cool! have you tried Tanstack DB and ElectricSQL? https://x.com/marcelohbairros/status/1956892684859158892
The whole line of Tanstack products is very well made yet poorly designed at the same time. I don't know if it's inherited from React by trying (and succeeding) to be a seamless React experience or if it's part of their own philosophy, but most of the tools make it very easy to mix state everywhere in your app which is just bad.
Really people should just move to Gleam and Lustre or Elm, even if it means I'll have much fewer clients paying good money to untangle state issues...
Re: Lessons learned from building a sync-engine and reactivity system with SQLite
#6It feels like everyone is solving the sync problem from a slightly different angle. Has anyone here used a few of these in production?
Re: Lessons learned from building a sync-engine and reactivity system with SQLite
#7> And because Electric syncs every change granularly, you are certain that the state of your local database is exactly the same as the server's.
I don't see how this certainty follows from "granularity" (whatever that means in this context). I believe to have such a certainty one would need the synchronization to happen within a single transaction that spans both client and server databases.
Re: Lessons learned from building a sync-engine and reactivity system with SQLite
#8Ok is this about a reactive app with with a local database automatically synced to a remote db? All fully encrypted (at rest and in transit)?
I thought this is what everyone does nowadays!
We built an app like this in 2019 - yes - it was a bit of a challenge with the encryption but the „syncing data“-part is what every litte multiplayer-game has to deal with like forever now. Seems i‘m out of touch with the current state of affairs.
Nice article though!
Re: Lessons learned from building a sync-engine and reactivity system with SQLite
#9It feels like everyone is solving the sync problem from a slightly different angle. Has anyone here used a few of these in production?
We use very similar solution in https://reflect.app
Using the wa-sqlite library, and our own Mobx-based model layer similar to what Linear does.
I gave a short talk about it a few months ago https://www.youtube.com/watch?v=b0GKWzeyZko
Re: Lessons learned from building a sync-engine and reactivity system with SQLite
#10FWIW, I think you might be better off with immutable rows and lamport clocks.
Everything is a full new row because it is “a message” including read receipts. Some messages like read receipts just don’t render in the chat.
Edits can work the same way by rendering over a previous message, even though the local and remote DB have multiple rows for the original and edited messages.