Comparison
Micro-frontendvsModule federation
Micro-frontend
three teams each own a section of one page and each deploys their section without the others.
Splitting a single interface into independently owned and deployed pieces, composed at build time, at the edge, or in the browser. It buys team autonomy on a large product and is usually adopted for that organisational reason rather than a technical one. It costs duplicated dependencies, an inconsistent interface unless design system discipline holds, and a debugging story that spans several repositories.
Full entry →Module federation
one deployed application loads a component from another at runtime, over the network, from its own build.
A bundler feature letting separately built and deployed applications share modules at runtime, including shared singletons of a framework. It lets teams deploy independently without publishing packages, which is its entire point. The cost is a distributed versioning problem in the browser: a shared dependency mismatch between two independently deployed hosts fails at runtime, in production, with no build to catch it.
Full entry →