Nuxt as the backbone of a scalable e-commerce platform
summary
Jumbo moves from a large monolith to a modular front-end platform built from a component library, a headless CMS (Adobe Experience Manager) with adapters, a Node.js content service that validates and routes content, and a Nuxt content renderer for SSR. Components generate meta files for the CMS, per-page bundles trim megabytes, and a single Nuxt instance now serves the homepage (over 100 page views/day) while reducing maintenance; basket reactivity across apps remains a known challenge.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:04Why Nuxt for Jumbo
- 2:50Company context overview
- 3:33Monolith to microservices
- 7:46Distributed architecture challenges
- 9:30Solutions for complexity
- 10:32Component library foundation
- 13:21CMS and adapter architecture
- 14:24Content service role
- 15:08Nuxt as frontend layer
- 18:18Content editor challenges
- 20:30Deployment and performance
- 21:12Modular landscape benefits
- 22:39Key takeaways and future
- 24:05Q&A: English site plans
- 25:08Q&A: Monolith migration downsides
- 26:55Q&A: Consistency across apps
- 28:22Q&A: Nuxt 3 migration
- 30:08Q&A: Scaling and onboarding
- 31:52Q&A: CMS and future plans
- 32:55Q&A: Nuxt 3 migration challenges
- 34:19Q&A
