React Server Components: Fad or Real Progress?
summary
Explains how React Server Components work in Next.js (React Canary) to keep some components at zero bundle size by running them on the server so they can call ORMs, APIs and the filesystem directly. Describes how HTML streaming + Suspense and selective hydration reduce client-server waterfalls, shows a demo with Next.js, Webpack and the PokéAPI (plus a client counter) to illustrate what ends up in the client bundle, and warns about risks like accidental server-code shipping (API key leaks), immature tooling, caching semantics, and the large carbon footprint tied to device manufacturing.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:05SSR vs CSR performance
- 4:58Hydration limitations
- 9:57Server Components theory
- 13:08Client Components practice
- 16:36Real server advantages
- 17:19Live demo
- 24:11Pitfalls and best practices
- 24:54Future of React
- 33:04Conclusion
- 35:15Q&A
related talks
43mReact Applications on the Server
54mReact Server Components: A New Way to Build Fast and Interactive Web Apps
44mReact Server Components 101
48mReact Server Components: A New Way to Build Fast and Interactive Web Apps
01h 07mDemystifying React Server Components
45mReact Server Components: A New Way to Build Fast and Interactive Web Apps
19mReact Server Components - Under the Hood
12mExploring the Power of React Server Components
