Micro-Frontend & Me, a love story
summary
Argues that microfrontends actually solve one concrete pain: independent team deployments, proven by interviews with companies of 50–200 engineers and a podcast episode that hit ~2,000 views; prescribes splitting by bounded contexts (DDD + Conway’s law), keeping a minimal shell, and choosing vertical vs horizontal composition depending on user journey; recommends tools like module federation, Single SPA, Piral or Web Components, TanStack Query, and event/URL-based state sharing; warns about added complexity, CSS isolation needs, and vendor lock‑in and says avoid MFEs for teams under ~5.
AI-written summary · about
chapters (24)
- 0:00Micro-frontends intro
- 2:20Frontend architecture evolution
- 3:46Why I rejected micro-frontends
- 6:38Birds Aren't Real reconsideration
- 8:06Pain points micro-frontends solve
- 9:30Problems micro-frontends solve
- 11:37Legacy systems & integrations
- 14:09When to avoid micro-frontends
- 15:11Splitting micro-frontends DDD
- 16:36Conway's law & teams
- 17:19Vertical vs horizontal MFEs
- 19:03Horizontal MFE complexities
- 21:51Module federation solutions
- 24:22Demo module federation
- 25:44Maintaining MFEs best practices
- 27:08Shell app anti-patterns
- 27:52State sharing strategies
- 28:56Design systems & CSS
- 29:38Tech stack diversity pitfalls
- 30:42Routing & performance
- 31:47When MFEs are overkill
- 32:08Focus on pain points
- 33:10Vendor lock-in challenges
- 33:32Resources & closing
related talks
22mMicro Frontends & me, a love story
47mDemystifying Micro Frontends
52mMicro frontends: prepare for the ride
34mMicro Frontends
29mMicro Frontends, how to evolve to an extensible frontend
29mMicro Frontends, or How to Evolve to an Extensible Frontend
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
27mMicro-frontends: anti-patterns