In detail
Micro-Frontends extend the microservices philosophy to the frontend. Instead of a single monolithic frontend application, the UI is decomposed into smaller, independently developed, tested, and deployed applications. Each team owns a vertical slice of the product -- from UI to API. At runtime, these micro-apps are composed into a seamless user experience using techniques like Module Federation (Webpack 5), iframes, or Web Components. This enables large organizations to scale frontend development across many teams without the coordination overhead of a monolith.
How it works
- 1
Domain Decomposition
The frontend is split along business domain boundaries (e.g., checkout, catalog, account) owned by separate teams.
- 2
Independent Development
Each micro-frontend is built with its own tech stack, build pipeline, and deployment cycle.
- 3
Runtime Composition
A shell application loads and composes micro-frontends at runtime using Module Federation or import maps.
- 4
Shared Contracts
Teams agree on shared APIs, design tokens, and routing conventions to ensure a cohesive user experience.
Where it is used
- Enterprise Portals
- Large organizations where different teams own different sections of a complex internal portal.
- Incremental Migration
- Gradually replacing a legacy frontend by building new features as micro-frontends alongside the old system.
- Multi-Team Products
- Products where autonomous teams need to ship independently without blocking each other.