Micro Frontends Made Easy with Module Federation
summary
Claims that Webpack 5 Module Federation lets many teams ship independently are backed by concrete details: version 2 adds hot module reload and crossed 1M weekly downloads, apps expose a remote entry and can share a single store so state updates propagate at runtime, not by redeploying. Microsoft’s Azure Pricing Calculator implements a cost card split into 150+ federated services, built over years and running in production to compose pricing UI from multiple deployments.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:41Micro frontends vs monoliths
- 3:05Monolith problems
- 4:55Micro frontend benefits
- 5:59Module Federation intro
- 7:02Module Federation features
- 8:26When to use Federation
- 9:02Demo: basic Federation
- 12:59State sharing in Federation
- 13:22Microsoft use case
- 15:10Azure pricing calculator
- 16:56Federated app communication
- 17:58Azure service separation
- 18:42Azure platform benefits
- 19:56Microsoft problems solved
- 20:39Solution with Federation
related talks
01h 13mThe Microfrontend Revolution, module federation, Webpack 5
35mMicro Frontends with Module Federation, Angular and Azure Static Web Apps
51mBuilding a Micro-Frontend Application with Webpack 5 Module Federation
28mModule Federation: Theory vs Practice
25mBeyond Micro Frontends - Three Additional Things Module Federation Makes Possible
31mModule Federation in Webpack 5
29mHow module federstion makes our life easier
55mModule Federation in 2024: Beyond Webpack