Microfrontends: Cutting Through the Hype and Misconceptions (w/ Luca)

Описание: Micro-frontends promise to help teams scale development, but AWS Principal Architect Luca Mezzalira has seen some succeed and some just fall apart. In this conversation, he shares what he's learned from years of implementation work at companies like DAZN and through consulting with Fortune 500 organizations.
Luca explains why micro-frontends are fundamentally different from components—something many teams get wrong from the start. He discusses the common pitfalls he encounters: teams treating them like distributed components, sharing state across boundaries, and copying architectures from companies with completely different constraints and resources.
The discussion covers practical implementation details—from communication patterns and tooling strategies to when approaches like iframes actually make sense. Luca also touches on newer developments in server-side rendering and how they're changing the micro-frontend landscape.
This isn't about micro-frontends being good or bad, but about understanding when and how to use them appropriately. Luca emphasizes the importance of context and organizational design in making these architectural decisions work.

Our Fantastic Guest - Luca Mezzalira
I’m a software architect with over 20 years of experience helping organizations—from startups to Fortune 500s—design scalable, resilient, and modern architectures. My focus: evolving frontend systems, driving cloud-native modernizations, and enabling autonomy at scale through architectural clarity.
As Principal Serverless Specialist Solutions Architect at AWS, I advise global enterprises on designing and implementing efficient, event-driven systems. I specialize in serverless, micro-frontends, and distributed architectures that align technology strategy with long-term business outcomes.

LinkedIn:   / lucamezzalira  
X/Twitter:   / lucamezzalira  

Chapters
0:00 Introduction and Guest Background
2:45 How would you describe micro-frontends like I'm five?
7:30 Is micro-frontends just copying microservices from backend?
12:15 What are we trying to scale with micro-frontends?
19:40 How do you manage team independence vs consistency?
28:50 Do you see different frameworks and versions in practice?
35:20 How do you handle shared information across micro-frontends?
47:15 What's the biggest reason people fail with micro-frontends?
52:30 How do you distinguish micro-frontends from components?
58:45 What are your thoughts on the signals proposal?
1:01:20 How do you see mono-repositories in this conversation?
1:06:15 What are clear indicators for when to use micro-frontends?
1:09:50 What are successful approaches for stitching micro-frontends?
1:11:00 Coffee culture: Moving from Italy to London

Links and Resources
Luca's Newsletter - https://www.buildingmicrofrontends.com/
Single-spa - https://single-spa.js.org/
Module Federation - https://webpack.js.org/concepts/modul...
Native Federation - https://www.npmjs.com/package/@angula...
Web Fragments (Microsoft) - https://github.com/microsoft/web-frag...
Astro Server Islands - https://docs.astro.build/en/concepts/...