Static eCommerce JAMstack
summary
Panelists debate whether static JAMstack actually scales for big eCommerce and offer concrete fixes: use Next for incremental static regeneration, push rendering and small personalizations to an edge worker personalization to avoid slow hydration, and run builds without clearing caches for sites with millions of pages. Companies demo orchestration to orchestrate legacy backends so a Sitecore or Magento origin remains while a CDN‑served front end takes over. Claims tie to measurable wins: faster Core Web Vitals, easier A/B testing, and shorter time‑to‑market.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 1:19Vercel strengths
- 5:12Storefront’s origin
- 9:08Performance focus
- 12:39Uniform’s role
- 17:15Static e-commerce challenges
- 23:10Hybrid rendering
- 30:30Personalization & A/B testing
- 37:35E-commerce future
- 47:23Web performance future
- 51:34Closing
related talks
24mEvolution of JamStack: Not just Static Anymore
35mThe Rise of JAMStack
42mTo Truly Understand Jamstack, Forget the JAM
56mJAMstack
44mJAMstack: Web Apps at Ludicrous Speed
58mFuture of eCommerce Panel 2.0
27mThe Post Jamstack World & the Rise of Hybrid Frameworks
17mMaintaining performance across a highly dynamic commerce site