Thayse Onofrio at LeadDev West Coast 2023
summary
Starts by extracting a small feature: extract to separate repo and publish as npm package which cuts PR conflicts but keeps version and deployment coupling. Then migrates to Module Federation with dynamic remotes to get independent deploys, lazy loading and feature-flagged AB tests. Demo composes a savings app and a profile app via a remoteEntry.js and shows it working with promise-based dynamic loading and fallbacks. Notes new pains: shared data/events, duplicate dependencies, version mismatches and who tests the composition, and suggests a shell app composes micro-frontends.
AI-written summary · about
chapters (16)
- 0:00Breaking apart monolithic front ends
- 2:11Problems with shared monolith
- 4:18Why micro front ends help
- 6:03Evolving vs rebuilding
- 7:07Bounded contexts defined
- 8:10Start small with npm extraction
- 9:33Independent deploys with Module Federation
- 11:19Dynamic loading via feature flags
- 12:44Handling failures in micro front ends
- 15:09Shell apps role in composition
- 15:52New challenges with micro front ends
- 17:36Avoiding duplicate dependencies
- 18:40Testing strategies for micro front ends
- 19:45Tradeoffs before adopting micro front ends
- 20:29Choosing approach and steps
- 22:14Micro front ends benefits and challenges
related talks
01h 13mArchitecting complex JavaScript setups for large scale enterprise projects
22mRoad to Module Federation
01h 17mChallenges in Building Micro Front Ends
36mMicro Frontends in Action!
45mMicro Frontends in Action!
47mDemystifying Micro Frontends
22mSetting up Enterprise Frontend for Success
29mHow module federstion makes our life easier