About & method
Built to tell you when the answer is no.
microfrontends.dev is a free, interactive guide for frontend engineers deciding whether their team needs micro frontends, and which approach fits if it does. It has no sponsors, no accounts and nothing to sell, so it can say “keep your monolith” when that’s the right call.
Who it’s for
One lesson, three depths
The core idea of each step in plain words, with a demo where one helps. No architecture background needed.
Adds how the idea plays out in practice: shared builds and releases, team boundaries, and what the sources say.
Adds the trade-offs behind the decision, such as pipelines, governance, performance budgets and migration.
Principles
What we hold ourselves to
Practising what it preaches
Why this site isn’t built with micro frontends
This site is built and maintained by one small team, ships as plain static pages, and has no need for independent deploys or several frameworks. By its own reasoning that is a case for a single, well-structured app, so that is what it is: a live example of the “you probably don’t need it” outcome.
How ratings work
A 1–5 judgement, always with a reason
Ratings compare approaches for a typical team. They are editorial judgements built from the sources we cite, not benchmarks, and every rating comes with a one-sentence reason and a source. See them side by side in the comparison matrix.
- Team independence
- Can teams build and deploy without coordinating?
- Runtime performance
- Impact on bundle size, requests and time to interactive.
- Complexity
- Setup and ongoing operational cost. Lower is better.
- SSR / SEO support
- How well it works with server rendering.
- Tech-agnostic
- Can different frameworks coexist?
- Isolation
- Style, script and failure isolation.
- UX consistency
- How easy it is to keep a consistent experience.
- Tooling maturity
- Ecosystem, docs and community.
How the decision check works
Transparent weights, no black box
- 10 questionsAbout your teams, releases, frameworks, performance needs and constraints.
- A readiness scoreAnswers add up to a score out of 100 that says how ready your team is for micro frontends.
- Rules can override itA few hard rules, such as “single team, single framework”, decide the outcome whatever the score.
- Reasons you can checkEach approach is scored on how well it fits, and every answer shows how it affected the result.
Every weight, rule and band is published in how the decision check works. Disagree with one? Open an issue on GitHub.
Policies
Rules we write by
- Every factual claim about a tool, its behavior or its status links to a primary source: official documentation, a specification, or the author’s own publication.
- No invented statistics, quotes or case studies. A claim that can’t be traced to a source is removed.
- Opinions and recommendations are labelled as the site’s view and kept apart from facts.
- Every comparison rating comes with a one-sentence reason and a source.
Every source the site cites is listed on Sources & method, with the pages that rely on it.
No ads, no paid content and no sponsors, and no ties to any tool, framework or vendor. Every approach gets the same template and the same criteria, including when to avoid it.
No accounts, no cookies and no analytics. Your decision check answers live only in the result link you choose to share, and we only have your email address if you subscribe. Read the privacy page.
llms.txt lists every page with a one-line summary, for language models and the tools built on them. Every page also has a Markdown version at its URL with .md added, andllms-full.txt holds the full text of every page in one file.
Found something wrong?
Corrections are the most useful contribution. Every lesson has a “Report an issue on GitHub” link that fills in the page for you, and the site’s content and code live in the GitHub repository, where every change is proposed as a pull request and reviewed before it goes live.
Open an issue on GitHub →