Micro-frontends: Is it a Silver Bullet?
summary
Migration to micro-frontends at AppsFlyer yields concrete tradeoffs: growth from 20 to 200 developers forces shared libraries that are hard to get right, a browser application wrapper becomes a single point of failure across 30 products, and duplicated work creates islands of knowledge. The team adopts Storybook and monorepo plus a front-end guild to share ownership; starting with module separation works, full micro-frontends scale only after organizational changes and heavy testing.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:30Microfrontends
- 1:06The Dark Side
- 1:27The Complexity
- 2:04About Liron
- 3:06Rapid Scale
- 3:29Microfrontend
- 4:37The Task
- 5:24Side Effects
- 6:14Example
- 8:36Failure
- 9:30Product Example
- 10:16Island of Knowledge
- 11:45Human Factor
- 12:18Community
- 12:51Summary
related talks
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
21mMicro-frontends: 3 years ago
29mMicro Frontends, how to evolve to an extensible frontend
34mMicro Frontends
25mMicrofrontends: a Modern Approach to Complex Web Applications
57mMicro Frontends – a strive for fully verticalized systems
25mMicro Frontend: a microservice architecture from your frontend web apps
52mMicro frontends: prepare for the ride