Micro-frontends: 3 years ago
summary
Company moves from 3–4 frontend devs to 500 and evolves micro-frontends from pure vertical to a mix of vertical hosts and horizontal components, merging two micro-frontends and splitting others as needed. Built a custom loader over SystemJS to load player and enable independent deploys and rollbacks. Uses a Backstage catalogue for discovery. Shares only critical cross-cutting pieces — payments/analytics/experiment libraries — and still avoids sharing visual components, keeping autonomy while reducing coordination pain.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:39Agenda → Once Upon a Time
- 3:12Once Upon a Time Part 1 of 4
- 3:38DAZN Engineering department was growing exponentially
- 4:58DAZN Micro-frontends Manifesto
- 6:28Domain Boundaries Evolution
- 7:40Some vertical Micro- frontends were too big for a single team
- 11:30Deep Dive into Horizontal Micro- frontends in DAZN
- 13:09Very autonomous Teams are at risk to create silos
- 13:37Share Knowledge across Teams
- 14:18Favor local decisions but have a plan for global decisions
- 15:21Enable Discovery beyond Teams
- 16:41Sharing Code Part 4 of 4
- 17:05Not a single visual component has been shared across all the Micro-frontends, yet
related talks
22mMicro Frontends & me, a love story
57mMicro Frontends – a strive for fully verticalized systems
34mMicro Frontends
37mDemystifying Micro-Frontends
33mMicro Frontends, Five Years After
24mMicrofrontends
41mMicro-frontends: the golden circle
13mMicro Frontends Without Chaos: Architecture That Survives Scale