Jamstack at Scale
summary
Jamstack struggles with build friction once sites hit tens of thousands of pages (REVOLVE 40,000 SKUs, Staples ~200,000, some catalogs >1,000,000) and frequent updates; claim: build time, AB testing and personalization, and Core Web Vitals break naive static builds. Concrete tools and fixes: Next.js ISG, Netlify/Vercel support, serverless SSR, saving artifacts, parallel image processing, and a tested workflow called parallel static rendering that preloads hot pages after deploy. CDN-side solutions include incremental static generation with stale-while-revalidate and edge A/B test splitting for fast, cache-safe personalization. Results: mixed but practical at large scale.
AI-written summary · about
chapters (15)
- 0:00Jamstack at Scale intro
- 1:20Challenges in Jamstack scale
- 2:44Build time friction
- 5:53Optimizing build times
- 7:39Client-side rendering trade-offs
- 10:08Incremental static generation
- 13:59Considerations for incremental static generation
- 16:07Serverless SSR at scale
- 18:38Jamstack architecture spectrum
- 19:44Parallel static rendering
- 20:47AB testing challenges
- 22:54Personalization strategies
- 24:42Performance pitfalls
- 26:30Core Web Vitals optimization
- 28:16Real user monitoring
