Real time server components
summary
Argues that stateful serverless replaces fragile request-only functions with edge processes using Durable Objects on Cloudflare and shows a working framework called React Party that exposes useState and context inside server components, runs over websockets, and broadcasts server-rendered component diffs. Demonstration uses a ~100-line server and ~100-line client, handles ~200 concurrent users in the demo, reports ~20 milliseconds edge latency, and integrates with Remix, Next, Waku and Redwood without rewriting apps.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 1:07Serverless model limitations
- 3:14Durable Objects explained
- 5:46Real-time chat room architecture
- 7:10Server components limitations
- 8:52Introducing React Party
- 10:36React Party features and use cases
- 11:40Integration with existing frameworks
- 12:01Live demo and closing
related talks
54mReact Server Components: A New Way to Build Fast and Interactive Web Apps
43mReact Applications on the Server
50mReact Server Components: A New Way to Build Fast and Interactive Web Apps
45mReact Server Components: A New Way to Build Fast and Interactive Web Apps
45mReact Server Components: Fad or Real Progress?
59mReact Server Components Explained for Backend Developers
40mServer-Side Rendering 2.0? React Server Components
25mThe Costs & Benefits of React Server Components
