Micro-frontends and module federation + Upgrades, migrations and tech debt
Comes up in: Frontend system design, Hiring manager
This concept is being written. It gets the full five steps — explanation, predict, interview angle, practice with tests, and review cards. Here is exactly what it will cover, so you can study it elsewhere in the meantime.
What it covers
- why and when (team autonomy) and the costs (duplication, consistency, performance)
- integration options (build-time packages, runtime module federation, iframes, web components)
- shared dependencies
- routing and design consistency
- planning a React 18→19 or Pages→App Router migration
- codemods
- incremental adoption
- measuring success
- communicating with stakeholders
Words you will know
What you will practise
- decide for/against micro-frontends in 3 company scenarios
- write a one-page migration proposal
Interview questions this answers
- What are micro-frontends? When are they a bad idea?
- How would you migrate a large app from the Pages Router to the App Router?