From Microfrontends and back
summary
Argues that microfrontends buy independent deploys and team autonomy but create testing, payload bloat, and coordination pain, so the team rebuilds a modular monolith using nx monorepo with apps/libs, an explicit dependency graph and ESLint rules, and an event-driven architecture implemented with RxJS (event bus, dispatchers, handlers) to keep modules loosely coupled yet cohesive. Recommends single framework, per-feature libraries, and reserves microfrontends for true scale (roughly 100+ developers).
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:53What will you learn
- 1:39What are Micro frontends?
- 3:43What are the benefits of Micro frontends?
- 7:17What are the consequences of these benefits?
- 12:41What do we need?
- 18:57What we have ended up doing?
- 19:39Nx Terminology
- 23:19What is EDA?
- 29:02How was it solved?
- 33:26Disclaimer
- 35:42What you have just learnt
