Splitting one UI across independently deployed teams. An organisational solution with real technical costs — worth knowing before you need it, and before you reach for it.
10 articles
Listed inMicrofrontend ArchitectureMicrofrontendson
Cam Jackson's reference article: the composition approaches side by side, a worked example of each, and an honest accounting of the costs.
Listed inModule FederationMicrofrontendson
The normative documentation for hosts, remotes, and shared scopes, now maintained independently of any one bundler.
Listed insingle-spaMicrofrontendson
The lifecycle contract every child application implements, plus the routing layer that mounts and unmounts them.
Listed inImport MapsMicrofrontendson
MDN on `<script type="importmap">` — bare specifier resolution in the browser, with no build step involved.
Listed inShared DependenciesMicrofrontendson
Version skew, singleton libraries that break when duplicated, and the payload you pay for twice.
Listed insingle-spaMicrofrontendson
A router that mounts and unmounts whole applications, so several frameworks can share one page.
Listed inImport MapsMicrofrontendson
The platform-native way to resolve bare specifiers in the browser — no bundler coupling, and no framework to adopt.
Listed inModule FederationMicrofrontendson
Loading code from another build at runtime: hosts, remotes, and the shared-scope negotiation underneath it.
Listed inComposition StrategiesMicrofrontendson
Build-time, server-side, and runtime composition — the choice that decides your coupling and your deploy story.
Listed inMicrofrontend ArchitectureMicrofrontendson
What the pattern actually buys — independent deploys per team — and the coordination costs that make it the wrong default.