Micro frontends anti patterns
summary
Argues micro‑frontends suit large, team‑scaled apps and lists concrete anti‑patterns: treating widgets as domains, the multi‑framework “hydra” as a temporary migration only, and embedding legacy hacks into the shell. Recommends concrete fixes: use an anti‑corruption layer, API‑first contracts, publish/subscribe via custom events or reactive streams, enforce unidirectional data flow, and route at the CDN edge for canary traffic. Reports results: fewer rollbacks and deployments rising from ~5–6/month to 25 per microfrontend per day.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:31A component
- 14:05The greenfield project...
- 15:18The legacy editor
- 23:47Design-time coupling
- 24:50Loosely coupled entities
- 27:10Your distributed system
- 28:55Possible solutions
- 30:31Migration strategies
