When micro-frontends pay off
Multiple business units sharing a shell (header, auth, analytics) but owning product verticals — checkout vs account vs admin — benefit from Module Federation or single-spa. The cost is shared dependency alignment and routing complexity.
We define shared React version policy, design tokens, and event bus contracts before splitting repos.
Production lessons
- Version skew breaks silently — automate compatibility tests
- Shared auth token refresh must live in shell or shared package
- Avoid micro-frontends for teams under 15 engineers — monorepo first
Module Federation for UX continuity; iframes only for untrusted third-party widgets.
Discuss your project with an architect
No spam — response within one business day.
Schedule Consultation →