Demystifying Micro Frontends
summary
Argues microfrontends solve team-scale pain when a monolith stalls, not a silver bullet; requires strict business-aligned boundaries, contracts and ~90% automated-test confidence. Recommends starting with build-time composition and an app shell for auth/config, then move to module federation once CI/CD and automation prove it. Uses TurboRepo + TanStack router/query in an SPA, ships a custom web element (Vue) as an npm package — build-time approach works, module federation adds smaller deployments but needs discipline.
AI-written summary · about
chapters (15)
- 0:00Introduction to Micro Frontends
- 1:10Why adopt Micro Frontends
- 4:00Benefits and challenges
- 7:51Key principles of Micro Frontends
- 12:25Application shell concept
- 15:40Vertical vs horizontal split
- 19:35Visualizing Micro Frontends architecture
- 24:10Tools and technologies
- 27:41Q&A: Downsides and complexity
- 30:53Q&A: Horizontal vs vertical split
- 35:39Q&A: App shell requirements
- 38:28Q&A: Hybrid design systems
- 43:25Q&A: Implementation process
- 45:53Q&A: Server-side rendering
- 46:56Closing remarks
related talks
52mMicro frontends: prepare for the ride
22mMicro Frontends & me, a love story
35mMicro-Frontend & Me, a love story
38mFrom Microfrontends and back
21mEmbracing Micro-frontends: A Comprehensive Guide for Modern Web Development
45mThe Problems Micro Frontends Won't Solve That No One Wants to Talk About
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
57mMicro Frontends – a strive for fully verticalized systems