Beyond the Hype: Facing Micro Frontend Challenges in Large-Scale
summary
Adopts micro frontends at scale triggers specific pain: coordinating roles across a shell and 70–100 services, keeping a consistent design system for 400–500 engineers, and stopping bundle-size and load-time regressions. Uses Storybook, bundle-phobia, semantic-release and Storybook for component truth, Datadog and Sentry for per-service metrics/alerts, and a Sourcegraph-like search. Builds an internal dashboard that tracks bundle size by version, fires Slack/on‑call alerts, and lets teams reproduce and fix errors before users see them.
AI-written summary · about
chapters (10)
- 0:00Introduction and overview
- 1:24What are micro frontends
- 2:54Key benefits of micro frontends
- 4:21Challenges in micro frontend adoption
- 6:31Roles and responsibilities
- 7:37Unified user experience
- 9:24Load time optimization
- 11:56Knowledge sharing and collaboration
- 14:29Monitoring and debugging
- 17:18When to consider micro frontends
related talks
26mBeyond the Hype: Facing Micro Frontend Challenges in Large Scale
40mScaling Frontend Development
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
22mMicro Frontends & me, a love story
14mMicro-frontends: Is it a Silver Bullet?
37mDemystifying Micro-Frontends
34mMicro Frontends
39mScaling Frontend Development