The Micro Frontend Architecture: How to Turn Your Website into a Giant Collaborative Puzzle
summary
A seven-year migration to micro frontends that moved six international e-commerce sites to a puzzle-like aggregator architecture using a registry/shaper/resolver stack and a back-office “designer.” The system uses multi-repo, multi‑tech choices with SSR (NestJS, Java with Zelt/FreeMarker), composes pages by streaming primary fragments, parallelizing fragment calls, and applying lazy-loading and partial hydration to reduce payloads and carbon. The result is an autoscaled cloud deployment with ~800 deployments/month, 99.95% availability, and measurable web performance improvements.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:34Web architectures overview
- 2:56Microfrontend approaches
- 5:03Team autonomy
- 8:12Key concepts
- 9:14Aggregator architecture
- 11:01Performance & resilience
- 16:41Resource loading optimization
- 19:08Rendering strategies
- 22:37Local dev experience
- 27:12Deployment & infra
- 28:56Environmental impact
- 32:04Progressive migration
- 33:50Observability & teams
- 35:37Results & conclusion
- 42:15Q&A
related talks
57mMicro Frontends – a strive for fully verticalized systems
13mMicro Frontends Without Chaos: Architecture That Survives Scale
25mMicro Frontend: a microservice architecture from your frontend web apps
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
21mMicro-frontends: 3 years ago
11mTransforming Enterprise Frontends with Micro-Frontend Architectures
25mMicrofrontends: a Modern Approach to Complex Web Applications
44mMicro Frontend: the microservice puzzle extended to frontend