What we learned rebuilding the largest Nordic electronic retail website
summary
Rewrites the Nordic retailer frontend in Next.js 14 and deploys on Vercel, done by a small team (six developers) after a two‑month proof‑of‑concept with three people. Picks server rendering over a client‑heavy Angular build, then moves from Edge to serverless because edge runtime adds latency at scale; switching one or two days before full roll‑out yields much better Core Web Vitals and PageSpeed scores. Uses middleware for per‑market routing, Vercel Edge Config and LaunchDarkly for flags, and server actions for simple client→server calls. Performance improves and costs are expected to drop.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 7:09Selling technical changes
- 17:11Next.js for the rebuild
- 23:30Edge runtime lessons
- 26:40Routing in Next.js
- 31:59Server components performance
- 36:59Internationalization middleware
- 41:14Feature toggling Edge config
- 44:25Server actions
- 47:19Caching strategies
- 49:31Partial rendering streaming
- 52:16Vercel deployment insights
- 54:48Summary
- 56:12Q&A
related talks
46mWhat we learned rebuilding the largest Nordic electronic retail website in Next js?
01h 01mLearnings from One Year in Production with Next.js on Vercel
22mOptimization strategies for a performant, headless storefront
28mThe Path to Scaling a Digital Enterprise
11mEnterprise-grade composable commerce with Next.js
17mThe Frontend Cloud: Crafting superior web experiences
43mScalable Multi-Tenant Frontend for an E-Commerce Platform
01h 14mJust Do Less