The Problems Micro Frontends Won't Solve
summary
Argues that micro frontends solve incremental rewrites and team autonomy but not code quality, sharing, or performance; lists concrete pain points: duplicate API calls and extra frameworks causing the application to tank and a backlog of over 20 forgotten bugs, memory leaks from missed teardown, and an untraceable Module Federation upgrade error that consumes weeks of senior dev time. Recommends Strangler pattern for incremental rewrites, consumer-driven contracts, strong DevOps, documentation and experienced front-end engineers before adopting micro frontends.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:51Understanding micro frontends
- 7:12Benefits and use cases
- 10:53Real-world scenarios and risks
- 25:00Limitations and challenges
- 32:17Successful implementation
- 39:12Q&A session
related talks
45mThe Problems Micro Frontends Won't Solve That No One Wants to Talk About
52mMicro frontends: prepare for the ride
38mMicro frontends anti patterns
27mMicro-frontends: anti-patterns
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
47mDemystifying Micro Frontends
34mMicro Frontends
35mMicro-Frontend & Me, a love story