The Path to Scaling a Digital Enterprise
summary
A news site moves from a crashing WordPress monolith to Next.js on Vercel, decouples publishing from presentation, and uses ISR, edge cache and a publish-event pipeline to avoid backend calls; it grows from 800→75,000 active sessions, publishes ~400 pieces/day and hits 1B annual pageviews, improves Core Web Vitals (from ~30/100) to AMP‑like repeat‑load speeds, uses one‑click rollbacks and cost alerts, and reports that the serverless stack and first‑party analytics materially cut operational pain and saved money.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:24Essentially Sports scale
- 2:26WordPress monolith scaling
- 4:53Decoupling publishing and readers
- 7:49Serverless stack adoption
- 9:55Serverless frontend to WordPress
- 12:45Infrastructure ownership costs
- 14:10Vercel team efficiency
- 16:18Core Web Vitals optimization
- 18:45First-party data analytics
- 20:52Cost monitoring for teams
- 22:19Serverless pricing trends
- 24:05Vercel impact on performance
- 25:55Font and image optimization
- 26:59Own your data advice
related talks
30mHow Next.js Scales to Millions of Pages with ISR
25mSpeed at Scale: Optimizing The Largest CX Platform Out There
01h 00mWhat we learned rebuilding the largest Nordic electronic retail website
46mWhat we learned rebuilding the largest Nordic electronic retail website in Next js?
17mSpeed at Scale: Optimizing The Largest CX Platform Out There
29mJamstack at Scale
33mWeb performance in large-scale applications
17mMaintaining performance across a highly dynamic commerce site