At DAZN, some devices could only get a new app version through a firmware flash. To get around that, Luca Mezzalira (Author of Building Micro-Frontends, fmr. Principal SA @ AWS) split the app's logic from its shell so the logic could update on its own, before micro-frontends even had a name.

Eight years later, an engineer from that team said the architecture never changed.

For his one idea, Luca breaks down how to draw micro-frontend boundaries that hold, and the mistake that quietly destroys them: sharing state.
We cover:
- Why micro-frontends are a distributed system, not a component library
- Why the most expensive mistake is sharing state across micro-frontends
- How to define micro-frontend boundaries that hold
- How to use AI skill files to enforce micro-frontend governance automatically
- When to skip micro-frontends and stay on a monolith
- How to unwind micro-frontends into a monolith without a no rewrite

Chapters:
00:00 Introduction
02:13 How Luca Built Micro-frontends Before They Had A Name
07:35 Why Complexity Moves From Code To Coordination
12:26 When To Stay On A Monolith
18:32 How to Contain Bugs To One Domain
23:02 The Most Expensive Micro-frontend Mistake
26:30 How DAZN Structured Teams Across 40 Devices
27:13 8 Years Without Redrawing A Micro-frontend Boundary
35:25 How to Unwind Micro-frontends Without A Rewrite

The Man Who Wrote the Book on Micro-Frontends