Micro-Frontends Anti-Patterns
summary
Over about three years of consulting across 100 teams, common failures surface: equating micro-frontends with reusable components, leaking a global state that creates design-time coupling, and letting the host know domain specifics. The concrete fixes are to design micro-frontends as context-aware independent deployables, define clear input/output contracts, keep the container to a minimal API surface, and use event-driven communication so teams can release without coordinating every change.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:20Common Mistake
- 3:30Optimizing for Different Dimensions
- 5:10Four Key Things to Consider
- 7:00Design Time Coupling
- 8:05Events
- 9:18Conclusion
related talks
28mMicro-Frontends anti-patterns
38mMicro frontends anti patterns
27mMicro-frontends: anti-patterns
57mMicro Frontends – a strive for fully verticalized systems
10mMicrofrontends done right
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
43mThe Problems Micro Frontends Won't Solve
39mPatterns for Micro Frontends