Syncing > Querying.

Anywhere you query for data you should consider syncing data instead.

CDN-backed syncing means your data loads faster you get real-time updates for free.

It's like having mini PG read replicas scattered across your system.

Tech entrepreneur. Founder @electricsql. Founder @gatsbyjs (acquired by Netlify). @kylemathews on Twitter

You define the "Shape" to sync — https://next.electric-sql.com/guides/shapes — more-or-less a SQL query.

Electric listens to the replication log from Postgres and sends updated operations to people subscribed to the shape.

hypertext veteran • /mud core dev @lattice

How do you know what subset of data to sync? How do you keep that synced data fresh/accurate?

What does changing state look like? Do you modify the local db optimistically, and then have server side rules for what updates can be synced? Or do you use a classic REST pattern for that?