Overview
Syllabus
0:00 - Introduction & The Challenge: Scaling from Monolith to a Global System
1:51 - Are You Designing Architecture or Assembling Libraries?
3:55 - The Official Micro-Frontends Definition Explained Business Subdomain & Independent Implementation
6:25 - Micro-Frontend vs. Component The Key Difference
9:40 - Heuristics: Why Reusability is a Form of Coupling
12:15 - Fast Flow vs. Reusability: Why Your Goal is Fast Flow
15:10 - Organizational Benefits: Incremental Upgrades & Decentralization
17:01 - Conway’s Law & Aligning Architecture with Team Topologies
20:05 - The Micro-Frontends Decisions Framework Identify, Compose, Route, Communicate
23:55 - Client-Side vs. Server-Side Composition Best Practices
27:01 - Why You Shouldn't Use Shared Global State Use Event Emitters Instead
30:30 - Application Shell Responsibilities & Guardrails
32:45 - The Context Problem: When an Iframe is the Right Safe Answer
37:40 - Platform Team Responsibilities: Automating Performance Budgets
40:44 - The Power of Independent and Incremental Deployment
42:40 - Introducing the Frontend Discovery Service Canary & Blue/Green for Frontend
46:05 - Micro-Frontends Anarchy Antipattern: The Problem with Tech Anarchy
47:30 - The Hard Truth: Duplication is Cheaper than the Wrong Abstraction
50:20 - Value-Stream Team Responsibilities: You Build It, You Own It, You Run It
Taught by
InfoQ