Do Frontend Devs dream of Backend functions?
summary
Claims that React 19 and Next 14 let frontends become full stack get unpacked with concrete tools and numbers — renderToPipeableStream streaming HTML, React Server Components returning serialized payloads, a partial PPR demo that mixes static shell plus streamed dynamic pieces, and a 5 second cache example that proves revalidation patterns. Problems shown include server action serialization, leaked secrets when server code goes client, and real security incidents reported by Sasha CI and a Netflix engineer.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:34React’s evolution to backend
- 4:27From SPAs to SSR
- 6:19Streaming in React 18
- 8:25React Server Components
- 11:58Multi-layer rendering
- 14:09Server-driven Next.js
- 16:40Caching for performance
- 19:30Server actions and boundaries
- 22:19Full-stack challenges
- 26:40Debugging hybrid React
- 30:38Abstraction layers
- 32:48Conclusions and future
- 34:39Q&A: SSR vs RSC
- 36:03Q&A: Server actions
- 37:51Q&A: Debugging RSC
- 38:52Q&A: Tooling for React
- 42:43Q&A: Next.js deployment
related talks
45mReact Server Components: Fad or Real Progress?
30mMicro Frontends in React — a State of the Art Approach
01h 10mThe Future of Frontend Panel
24mAriel Shulman @ ReactNext '25
54mReact Server Components: A New Way to Build Fast and Interactive Web Apps
46mFunctional Frontend. Practical survival guide for backend engineers.
35mGoing fullstack React(ive)
59mReact Server Components Explained for Backend Developers