Approaches · 7 + 1 alternative
Ways to put a frontend together
From one app with clear modules to fully isolated iframes. Each card rates complexity, team independence and runtime performance from 1 to 5. Open one for how it works, the trade-offs and the reasoning behind every rating.
All approaches
- Build-time
Build-time packages
Versioned npm packages, built into one bundle.
complexity1independence2performance5 - Runtime
Module Federation
Separate bundles, loaded at runtime with shared deps.
complexity4independence4performance3 - Runtime
Native Federation / import maps
Plain ES modules wired up by an import map.
complexity3independence4performance3 - Runtime
single-spa
A root router that mounts apps in any framework.
complexity4independence4performance2 - Runtime
Web Components
Custom elements as the contract between teams.
complexity3independence3performance3 - Runtime
iframes
Each app in its own frame. Total isolation, full cost.
complexity2independence5performance1 - Server
Server and edge composition
HTML fragments stitched on the server or edge.
complexity4independence4performance4 - Alternative
Modular monolith and monorepo
One app, one deploy, team-owned modules.
complexity2independence2performance5
Ratings 1–5 are editorial judgement for a typical team. Complexity: higher means harder to build and run. Independence and performance: higher is better.