Learnings from One Year in Production with Next.js on Vercel
summary
A Next.js rewrite on Vercel cuts user flows from two minutes to about 30 seconds—roughly a 75% speed improvement—by removing a CDN proxy, favoring static server rendering, and pushing logic to Vercel Edge with middleware. The stack uses LaunchDarkly + Vercel Edge Config for feature flags, Turbo Repo and a shared design system to speed builds, and micro-frontends via Vercel microfrontends/multizone for per-route previews. The demos show cached dynamic-ish pages, safe flag rollouts, and fast deploy rollbacks working in production.
AI-written summary · about
chapters (16)
- 0:00Introduction and background
- 5:53Business impact of performance
- 7:25Iteration speed and feedback loops
- 10:18Application structure and modularity
- 13:34Using Turbo for monorepos
- 16:00Design system importance
- 18:26Measuring web performance
- 22:23Network latency and CDN impact
- 25:10Static vs client-side rendering
- 27:19Prerendering and middleware
- 29:26Feature flags and toggles
- 32:56Micro frontend demo
- 47:17Middleware for dynamic pages
- 52:14Personalization and caching
- 55:27Flag SDK and static flags
- 59:07Summary and key takeaways
related talks
01h 00mWhat we learned rebuilding the largest Nordic electronic retail website
55mWhat we learned rebuilding the largest Nordic electronic retail website in Next.js?
33mVercel + Vue.js
12mNext.js at the Edge
01h 14mJust Do Less
18mBuilding for Non-Profit Communities with Vercel and Next.js
32mLiving on the Edge
26mBuilding for the Edge