Advanced ยท 4h 54m ยท 20 lessons
Micro Front-ends
Split a large frontend into independent pieces owned by different teams.
What you'll learn
- โฆExplain what a micro-frontend is and the team problem it solves
- โฆDescribe what the app shell owns and choose a composition method for a page
- โฆCompare build-time and run-time composition and explain how Module Federation loads a remote
- โฆDesign how pieces share state, styles, routes and events without coupling to each other
- โฆDecide which libraries to share, how to load pieces fast and how to ship one piece on its own
- โฆContain a failing piece, version the contracts between pieces and judge when a team should adopt micro-frontends
Part of these career paths
- Frontend Developer path ยท course 8 of 8
Certification projects
Build 4 projects to earn your certificate
Hands-on work that proves you can apply what you learned โ part of the certificate requirements.
Syllabus
Module 1 ยท 53m
What are micro-frontends? Free
What you'll be able to do
- Can explain what makes a piece of UI a micro-frontend, and tell it apart from a shared component or a microservice
- Can name the team pains micro-frontends fix (a shared release train, a gradual migration) and the costs they add
- Can decide when one SPA or a modular monolith is the better choice, and say why code size alone is not a reason to split
Module 2 ยท 1h 2m
Composing them Locked
What you'll be able to do
- Can list what the app shell should own (layout, nav, login session, routing, loading pieces) and spot business logic that has leaked into it
- Can explain when the pieces come together in build-time, server-side and run-time composition, and pick one for a team set-up
- Can read a Module Federation config and trace how a host loads a remote and shares React
- Can match iframes, Web Components, single-spa and import maps to the need each one fits
Module 3 ยท 55m
Cross-cutting concerns Locked
What you'll be able to do
- Can decide which data pieces share, who owns each value, and whether it travels as props, events or the URL
- Can write an event contract (name, payload, version) and explain why a late-loading piece misses an event
- Can stop CSS collisions with CSS Modules, prefixes or Shadow DOM, and give every route prefix one owner
- Can keep many pieces feeling like one product with a versioned design system and the right version bumps
Module 4 ยท 40m
Performance & delivery Locked
What you'll be able to do
- Can decide which libraries to share between pieces, and work out how many bytes sharing saves
- Can lazy-load pieces by route and calculate what a page downloads first
- Can ship, cache and roll back one piece without touching the others
Module 5 ยท 41m
Reliability & ownership Locked
What you'll be able to do
- Can contain a failing piece with error boundaries and fallbacks, and say which errors they miss
- Can version a piece's contract and change it without breaking other teams
- Can split teams by feature and give every piece, including the shell, a clear owner
Module 6 ยท 43m
Making the call Locked
What you'll be able to do
- Can decide whether to adopt micro-frontends by counting blocked teams and waiting, not lines of code
- Can start with a modular app and plan a route-by-route migration when the split is due
- Can build and debug a first Module Federation demo and plan the next month of practice
More Web courses