Web Architecture for IKEA.com – Present/Future
summary
IKEA.com runs a static-files architecture with over 40 million files and 50 frontend teams, serving ~66% of traffic as static content; A/B tests use deterministic bucketing (concat user ID + experiment, hash with murmur3 deterministic bucketing) but client-side swaps cause CLS spikes (example 0.26). Moving rendering to Edge lets HTML vary per bucket without flicker; two production examples removed ~1M per-market files for payments and added social-preview metadata via CDN Edge (Rust) with 10 ms avg compute (payments) and 3.5 ms (preview).
AI-written summary · about
chapters (8)
- 0:00Introduction to IKEA.com
- 3:18Static sites and their challenges
- 8:12A/B testing with static sites
- 12:28Moving to dynamic responses
- 18:29Why Edge Computing
- 21:37Edge computing in production
- 25:35Future of personalization
- 30:09Key takeaways and Q&A
related talks
40mMicroservice Websites
17mPerformance Engineering in Dynamic Web
29mModern Websites for E-commerce in the Real World
43mHundreds of components, hundreds of experiments and only one page
29mJamstack at Scale
52mStatic eCommerce JAMstack
47mThe Micro Frontend Architecture: How to Turn Your Website into a Giant Collaborative Puzzle
45mFrontend Perfor