Micro Frontends at Scale: What Works and What Does Not

Micro frontend architecture has picked up a lot of interest over the last few years, but going from a working prototype to something running in production brings challenges that most tutorials quietly skip past.

The core promise is real: separate teams can deploy their own vertical slices of the UI without waiting for a single frontend release cycle. Module Federation, iframes, web components, and server side composition all give you that, but each comes with tradeoffs around bundle size, runtime isolation, and shared dependency management.

In practice the hardest problems are cross app navigation state, shared authentication tokens, and keeping a consistent design system. When two apps disagree on the version of React or the design token surface you end up debugging runtime incompatibilities instead of shipping features.

The patterns that hold up in production: a shell application that owns the auth context and publishes it via a typed event bus, strict shared nothing policies for business logic, and a centrally managed design token package with a clear semver contract that all apps treat as a peer dependency.

Build federation around domain boundaries rather than team boundaries and deployment independence tends to follow on its own without requiring a lot of painful integration work at the shell level.