Making React Fun Again, with Sync Engines
summary
Argues that replacing REST APIs with sync engines (Zero, Electric, Power Sync) yields instant reads and writes across an app by preloading and pushing changes from the DB; demoed a production bug tracker (zbugs) with ~1,000 issues used six months and responding next-frame. Electric spins up a Postgres source in ~15 seconds, Power Sync in ~10 minutes, Zero offers dynamic typed queries and server/client custom mutators and targets 25–100 MB client cache for full-stack reactivity.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:41The problem with React
- 6:22Architecture of sync engines
- 9:01Demonstration of sync engine
- 12:01Working with sync engines
- 25:24Interoperability and conclusion
related talks
18mThe need for speed - Single-page apps, Optimistic UIs, Reactivity
24mZero-Latency React Native: Apps Without Loading Spinners
34mBuilding a Sync Engine in Clojure
31mReact Server Components Elevating Speed, Interactivity, and User Experience
02h 50mReact: Internals and Advanced Performance Patterns
38mThe Front End Architecture Revolution
01h 00mEffective React: Lessons from 10 Years
01h 08mData sync for realtime or offline apps with React and GraphQL