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.

What is fundamentally interesting about the shift from query -> sync?

Both answer the question: "how do I copy data from the database?"

Sync gives you two huge advantages:

1. built-in caching so cheap distribution of data via CDNs
2. real-time updates so no stale data

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

What is your favourite specifics in a stack to pull off this strategy?

ElectricSQL is a CDN-native Sync Engine for copying data from Postgres to anywhere you need it.

It's real-time Postgres exposed over HTTP w/ standard cache-control/etag headers.

Building /structs for the sentient

playstructs.com

Nvm, found it 😅

https://warpcast.com/kam/0x9fe1d3fc