Micro-Frontends Decisions Framework
summary
Claims a four‑decision framework that becomes hard to change later and delivers concrete tech choices: choose horizontal vs vertical split (vertical suits <10 teams), pick composition: client side, edge side include or server side, and own deployment boundaries; recommends Module Federation for shared dev DX, use CDNs/S3, Lambda@Edge or cloud functions for routing, prefer event streams (not global state) for cross‑microfrontend comms, store JWT in cookies/session, use Sentry/LogRocket/NewRelic for observability, and favor web components for design systems.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:10What is a Micro-Frontends?
- 5:49Micro-Frontends Principles
- 9:48Key Micro-Frontends decisions
- 10:11Define a Micro-Frontend
- 15:13Compose Micro-Frontends
- 18:37Routing Micro-Frontends
- 20:01Micro-Frontends Communication
- 22:10More challenges to face...
- 27:00Resources
related talks
52mMicro frontends: prepare for the ride
37mDemystifying Micro-Frontends
57mMicro Frontends – a strive for fully verticalized systems
19mHarnessing Microfrontends: Platforms for Web Apps
22mMicro Frontends & me, a love story
26mTo Micro Frontend or Not to Micro Frontend
34mMicro Frontends
36mMicrofrontends: Scalability Savior or Unmanageable Maze?