The beauty of sync engines: 📝 update on one client 🌐 HTTP POSTs to API server 🗃️ API updates the DB 📜 DB feeds changes to WAL (write ahead log) 🔁 sync engine picks up WAL and feeds data to subscribed clients 💻 long polling clients update their own... local state 0ms changes.show more

Why this is cool: - a single generic endpoint akin to a /graphql POST (define the schema, stuff just works™️) - the server is still the source of truth in the DB - there's no loading status on the data, no Promise (ie no loading spinners) - multiplayer for free

Automate up to 70% of your customer support today. Save time and help your users find answers quickly. Try now at

But what if ✨everything was database ✨

This demo is super cool! Love the concept of just dissolving everything away to run in the database server. Feels like it's the eventual end state of everything

Built this one with sqlsync Can try it at

Will definitely look into it!

Every other week we toy with the idea of starting an electric migration hahaha

Haha yeah I need to wait until a stable release before I deal with another migration 😂

R u using zero

This is Electric + Tanstack optimistic

What are the advantages to this over an API writing to a WAL? Wouldn't this tightly couple your DB design to your business logic or is that not a big deal?

The DB maintains the ACID rigamarole and queryability that a normal app benefits from so you can decide what things to sync I think is the idea. If a table doesn't need to be synced live you can still query it just fine but they run on the same pipes.