Extending reactivity to the server with Convex
summary
Convex is a backend-as-a-service that extends UI reactivity to server and database by letting developers write backend functions in TypeScript with autocompletion and zero cold starts. It tracks runtime read sets (rows and index ranges accessed) to trigger selective cache invalidation, giving consistent client views and transactional snapshots across endpoints. Demos show counters and a cart auto-updating across browsers without manual pub/sub; contrasts include trpc/drizzle/T3 where frontends must invalidate or build websockets/Postgres listen‑notify plumbing. Claims low latency and simpler correctness for live apps.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:07Reactive frontends without server
- 3:40Old-school vs reactive frontend
- 6:36Server state challenges
- 8:24Manual reactivity graphs
- 11:57Convex for server reactivity
- 13:47Convex's reactive graph
- 15:13Consistent client views
- 17:20Distributed systems in frontend
- 19:48Pitching Convex to devs
- 20:51Convex's cache invalidation
- 23:01Convex vs other backends
- 25:09Real-world Convex use cases
- 26:34Benefits of Convex
- 29:04Convex challenges
- 31:09Learning Convex
related talks
01h 02mConvex: Life Without a Backend Team
14mReactive state for the backend
20mSupercharge Your Full-stack App with a Reactive Database
31mReact Server Components Elevating Speed, Interactivity, and User Experience
38mThe Front End Architecture Revolution
31mDecoupled, Not Disconnected: State and Sync in Micro-Frontends
35mHydration, Islands, Streaming, Resumability... Me, Oh My!
15mReactifying your application