Serving content on the web: from PHP to RSC—and beyond
summary
Argues that network round trips are the single most expensive operation and demonstrates with Spotify for Artists how dozens of separate service calls build one page. Compares server rendering approaches: Next/React Server Components rehydrate but revalidateTag forces full RSC rerender, Remix loaders invalidate whole layouts, sequential loaders create waterfalls. Presents isomorphic loaders in Solid Start and TanStack Start that marry server initial render with client-side React Query, including single-flight mutations and tighter cache-aware revalidation. Recommends streaming selectively.
AI-written summary · about
chapters (12)
- 0:00Introduction and History
- 1:04The Server-Driven Web Era
- 2:35Complex Data and Interactions
- 4:39The jQuery and SPA Shift
- 6:37Trade-offs of SPAs
- 8:30Server-Side Rendering Challenges
- 11:02Remix and Second-Gen Frameworks
- 13:24Next.js App Directory and RSCs
- 14:51Return to Client Data Loading
- 16:32TanStack Start and Isomorphism
- 19:12Performance Pitfalls and Fixes
- 20:36Conclusion and Streaming
related talks
24mServing content on the web: from PHP to RSC—and beyond
44mServer Side Rendering from the trenches
51mDiscussion on React server components
21mImplementation and use cases of modern rendering patterns
24mAriel Shulman @ ReactNext '25
24mRSCs In Production: 1 Year Later
27mAnd Now You Understand React Server Components
59mReact Server Components Explained for Backend Developers