Micro-frontends: anti-patterns
summary
Claims that Micro-Frontends enable incremental upgrades, team decentralization and independent deploys, with domain-aware bundles that communicate via event emitter or custom events. Warns concrete anti-patterns: confusing tiny components for micro-frontends, adopting multiple UI frameworks that bloat bundles, and sharing a global state that creates organizational coupling. Demonstrates tools and patterns: Module Federation for lazy loading but avoid bi-directional sharing, SystemJS entry points, and an anti-corruption iframe container to integrate legacy editors while keeping APIs and costs from cascading.
AI-written summary · about
chapters (7)
- 0:00Start
- 5:30A component
- 8:16A micro-frontend
- 13:18The greenfield project...
- 14:18The legacy editor
- 21:24Loosely coupled entities
- 23:10Your distributed system
related talks
28mMicro-Frontends anti-patterns
38mMicro frontends anti patterns
11mMicro-Frontends Anti-Patterns
52mMicro frontends: prepare for the ride
34mMicro Frontends
29mMicro Frontends, how to evolve to an extensible frontend
57mMicro Frontends – a strive for fully verticalized systems
45mMicro Frontends in Action!