Treat your users right with segmented rendering
summary
Argues that authenticated or personalized pages can be served cheaply by prebuilding a small set of segment-specific pages instead of per-request SSR, using cookies or session tokens to map users to a segment and one static render per segment to serve millions. Shows concrete tooling: Next.js Incremental Static Regeneration, edge handlers for per-request routing, cookie-based segment keys and cache keys, and cache/ISR configuration that makes personalized static sites practical and low-cost.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:35Server-side rendering limits
- 8:09User-specific URL parameters
- 11:33Stargate JS middleware
- 13:00Demo: static user content
- 16:35Segment detection and pages
- 19:05Incremental static generation
- 21:01Theme switching
- 22:03Edge personalization overview
- 23:30SSR and caching future
- 27:00Q&A
related talks
21mImplementation and use cases of modern rendering patterns
20mAdvanced Rendering Patterns
25mNext.js: Choosing an Optimal Rendering Pattern for your Application
27mSSR & SSG in NextJS
30m50 shades of React rendering with Next.js
30mIncremental Static Regeneration: Static sites on steroids
14mIntroducing Edge Slice Rerendering
22mOptimally using third-party services with Next.js