Micro frontends: Unbelievably True Life Story
summary
A real-world enterprise migration from a 2019 single-page Angular monolith to microfrontends is described: new features were packaged as web components, a shared core Angular/runtime was provided via a central bundle and webpack externals, and later Module Federation was adopted. The migration yielded roughly ~1 MB saved per component and improved hiring and feature delivery, while increasing build times, CI/CD complexity, and requiring extra work on dependency versioning and runtime code restructuring.
AI-written summary · about
chapters (12)
- 0:00Micro frontends intro
- 5:00Why we chose micro frontends
- 6:21First Angular component
- 7:49Converting to web components
- 8:55Micro frontend interactions
- 10:01Optimizing dependencies with Webpack
- 11:46Shared core for dependencies
- 14:14Dynamic component dependencies
- 15:38Module federation for code sharing
- 18:52Further optimizations
- 20:17Results and conclusion
- 21:25Q&A
related talks
48mMicrofrontend Architecture – technical implementation.
11mTransforming Enterprise Frontends with Micro-Frontend Architectures
24mMicrofrontends
25mMicro Frontend: a microservice architecture from your frontend web apps
47mMicro Frontends Unmasked
21mMicro-frontends: 3 years ago
31mMigrating from Monolith to Microfrontends
25mMicrofrontends: a Modern Approach to Complex Web Applications
