Micro-Frontends anti-patterns
summary
Lists the concrete anti-patterns and concrete fixes: confusing microfrontend vs component (components leak many props; microfrontends map to business subdomains), mixing frameworks only as a short migration strategy, and creating a “Swiss Army knife” container that forces postMessage plumbing — solved with an anti-corruption layer. Warns against shared core libraries and inheritance-style extensions, recommends composition over inheritance, enforces unidirectional data flow and independent state per microfrontend, and consolidates duplicate API calls to avoid backend overload.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:39A component
- 9:40Frameworks, frameworks everywhere!
- 11:59The greenfield project...
- 12:36The legacy editor
- 17:05The core library...extended and upgraded
- 17:55Decouple your libraries
- 21:37Design-time coupling
- 22:28Loosely coupled entities
- 23:52Your distributed system
- 25:14Possible solutions
related talks
27mMicro-frontends: anti-patterns
38mMicro frontends anti patterns
11mMicro-Frontends Anti-Patterns
52mMicro frontends: prepare for the ride
30mWhen to Use Microfrontends? (and When to Avoid Them!)
43mThe Problems Micro Frontends Won't Solve
57mMicro Frontends – a strive for fully verticalized systems
34mMicro Frontends