Building Scalable Multi-Tenant Frontend Architecture for a B2B E-Commerce Platform
summary
A single frontend replaces per-tenant Fargate stacks by running Next.js on Vercel at the CDN edge, cutting infrastructure duplication and onboarding time; the app consumes existing AWS APIs and uses middleware domain-to-tenant lookup to map custom domains to tenants. Pages use ISR with cached responses and background regeneration to avoid cross-tenant cache leaks, preview deploys per Git branch speed QA, and a public GitHub reference implementation demonstrates the approach in production.
AI-written summary · about
chapters (8)
- 0:00Multi-tenant frontend intro
- 3:19Single-tenant challenges
- 7:07Identifying tenants in requests
- 10:51Caching with Next.js middleware
- 13:26Tenant routing and SSR caching
- 16:05Final architecture on Vercel
- 17:08Benefits and improvements
- 37:08Q&A
related talks
43mScalable Multi-Tenant Frontend for an E-Commerce Platform
22mArchitecting Multi-Tenant Solutions with Next.js and the App Router
22mMulti-Tenant Frontend Architecture with Nuxt.js
25mMicrofrontends: a Modern Approach to Complex Web Applications
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
17mMaintaining performance across a highly dynamic commerce site
17mThe Frontend Cloud: Crafting superior web experiences
21mMicro-frontends: 3 years ago