Micro Frontends & me, a love story
summary
Adopts micro-frontends to enable independent deploys across teams, citing companies that run 60–70 micro frontends in production and a 10-engineer startup plagued by monthly CI/CD pipeline halts. Describes vertical (route-as-SPA) versus horizontal (multiple frontends per page) architectures, recommends starting vertical, using an event bus for communication, module federation, Piral, Web Fragments or Zephyr Cloud for orchestration, shadow DOM/CSS modules or Tailwind for styles, TanStack Query for shared API caching, and warns of vendor lock-in and significant infra cost.
AI-written summary · about
chapters (11)
- 0:00Introduction and birds
- 2:17Evolution of frontend architecture
- 4:02Why I initially rejected micro frontends
- 6:11Real-world adoption of micro frontends
- 7:36Problems micro frontends solve
- 10:47Challenges of micro frontends
- 11:30How to start with micro frontends
- 12:56Vertical vs horizontal micro frontends
- 15:44Building micro frontends: tips and tricks
- 19:18Key considerations before adopting
- 20:23Final thoughts and resources
related talks
35mMicro-Frontend & Me, a love story
21mMicro-frontends: 3 years ago
47mDemystifying Micro Frontends
52mMicro frontends: prepare for the ride
57mMicro Frontends – a strive for fully verticalized systems
34mMicro Frontends
37mDemystifying Micro-Frontends
36mMicrofrontends: Scalability Savior or Unmanageable Maze?