Fifty teams shipping frontend code independently sounds like a dream. Then React 17 and React 18 collide at runtime, your design system has six competing “latest” versions in production simultaneously, and a shared header owned by nobody quietly breaks for 30% of your users.
This is the real problem with micro frontends at scale. The pattern isn’t complicated. The governance layer — the shared kernel, versioning contracts, the theming system that can’t shatter when Team 47 deploys on a Friday — that’s where things fall apart. Here’s how to actually structure it.