Micro frontends: prepare for the ride
summary
Argues micro frontends solve organizational scaling but create concrete tech and process trade-offs: dependency sprawl, coordination overhead, infrastructure ownership, design-system drift, and tooling gaps. Recommends trying Module Federation (Webpack 5) or single-spa for gradual experiments, migrating low‑traffic pages first, and expecting runtime vs build‑time sync problems for cross‑microfrontend features. Notes a real pain: a shared header with ~70 configurable keys that prompted decomposition, and stresses documenting architecture decisions and creating cross‑team forums to avoid repeating mistakes.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:08Quick check
- 1:48Micro frontends
- 2:37Who am I
- 3:17Project start
- 5:23Backend vs frontend
- 6:52Law of diminishing returns
- 10:20Dan Abramo
- 11:20QA
- 14:43Benefits
- 19:40Four foundational pillars
- 22:05Organizational challenges
- 23:46monolithic frontend
- 26:00peoples example
- 31:20technical challenges
- 38:05recommendations
- 40:55development velocity
- 43:27should micro frontends be able to start independently
- 44:43different approaches of composing apps
- 46:03migration to micro frontends
related talks
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
27mMicro-frontends: anti-patterns
47mDemystifying Micro Frontends
48mMicrofrontend Architecture – technical implementation.
34mMicro Frontends
22mMicro Frontends & me, a love story
35mMicro-Frontend & Me, a love story
43mThe Problems Micro Frontends Won't Solve