Interactive guide · 3 lessons · 8 approaches
Micro frontends, what are they and do we need them?
Learn the idea in short, layered lessons, then see how each approach works and how they compare. Answer 10 questions and get an honest recommendation for your team.
10 questions · nothing stored · share your result as a link
An honest note
For many teams, the answer is no — and that’s fine.
Micro frontends trade a simple build for team independence. If one or two teams share a codebase, a well-structured modular monolith usually ships faster. When that’s true for you, this site will say so.
When not to use micro frontends- 1–2 teamsModular monolith
- shared releaseBuild-time packages
- teams blockedConsider micro frontends
Start anywhere
Short steps, one idea at a time
Every lesson is a sequence of small steps: read a little, open more depth when you want it, check yourself. Nothing is saved — come back any time.
Fundamentals
What micro frontends are, the problems they solve, and when not to use them.
3 lessonsApproaches
From npm packages to Module Federation to iframes — how each works and when to avoid it.
8 approachesCompare
Every approach rated on the same criteria, each rating with its reason and source.
8 criteriaDecision check
10 questions about your teams and constraints. A recommendation with reasons.
10 questionsGlossary
Every term in one sentence, linked to where it’s taught.
27 terms
One visual language
Learn the picture once
The same colors and shapes mean the same thing in every lesson and diagram. Labels are always written out — color is never the only signal.
- ShellThe host page: layout, routing, loading the others.
- Team A appA feature owned and deployed by one team.
- Team B appAnother team’s feature, on its own schedule.
- Shared depsReact, a design system — code everyone relies on.
- dashed line = runtime request
- solid line = build-time
- v2.1badge = version
- bar = bundle size
Still deciding?
Get an answer for your team in 10 questions.
Tell it about your teams, releases and constraints. You get a recommendation with its reasons — including “don’t” when that’s the honest answer.
- A recommendation with the reasons behind it
- Nothing stored — answers stay in your browser
- Share your result as a link
Project updates
Hear what’s new.
No schedule, no digest. Just a short note when something new is live.
- New lessons, approaches and tools as they ship
- No sponsors, nothing to sell
- Unsubscribe from any email in one click
Your address goes only to our mailing list. You confirm once, and every email has an unsubscribe link. How we handle it