// the find
neuland/micro-frontends
extending the microservice paradigms to web development
This is a reference site and example repo for the micro-frontends architecture pattern — splitting a frontend monolith into independently deployable vertical slices, one per team. It's aimed at frontend architects and engineering leads dealing with scaling frontend development across multiple teams. Think of it as the canonical written explainer for this approach, not a framework.
The three progressive code examples (client-only composition, universal/SSR, data-fetching) each build on the previous one using Web Components and nginx, which makes the tradeoffs concrete rather than theoretical. The 'team-red/green/blue' demo structure mirrors real organizational splits, so the org chart problem is front and center rather than buried. The universal composition example using custom elements with SSR hydration is a practical middle path that avoids the full complexity of module federation. The author also wrote a book on this topic, so the explanations have real depth behind them.
The repo is fundamentally a website with embedded demos, not a usable library — there's nothing to npm install. The code examples are intentionally minimal (vanilla JS, no build tooling), which means the hardest real-world problems (shared design systems, auth propagation across fragments, cross-fragment state) are not addressed. Last meaningful commit is years old and the examples predate the module federation era entirely, so anyone comparing this to Webpack 5 Module Federation or import maps will find gaps. No tests anywhere in the example code.