Mo Frontends Mo Problems Mo Solutions
summary
A consultancy builds microfrontends with Turborepo on Vercel because Module Federation wasn’t supported, then ships a TurboPack-based prototype that only works vertically, duplicates TS configs, and forces manual sync across apps; dependency sharing, unit-test mappings, and deployment portability break repeatedly so the team ends up reconsolidating parts back into a monolith. Comparisons show module federation can share libs and host Vue inside React, Vite and RSpack trade plugins for speed, and overall there’s significant operational overhead.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:31Micro frontends in the 90s
- 3:18Team dependencies solved
- 4:25Vercel and TurboRepo challenges
- 6:34Vertical vs horizontal limits
- 9:06Design system components
- 10:11Dependency chaos
- 11:33Module Federation solution
- 13:43Vite for performance
- 15:28Rspack vs Webpack
- 16:56Trade-offs and complexity
- 18:09Q&A on shell dependencies
- 21:05Deployment strategies
- 22:55Breaking changes logic
- 23:17Monolith vs micro frontends
- 25:05Large teams scalability
- 26:09Mixing frameworks
- 27:15Next.js app router
- 28:21Dependency management
- 29:26Final thoughts
related talks
15mA comparison on Microfrontends composition techniques Module Federation
47mDemystifying Micro Frontends
25mShipping Federated React Applications
45mMicro Frontends in Action!
47mMicro Frontends Unmasked
52mMicro frontends: prepare for the ride
01h 17mChallenges in Building Micro Front Ends
36mMicrofrontends: Scalability Savior or Unmanageable Maze?