SSR with Micro-Frontends: How Composition Works with Modern Frameworks
summary
Claims that server-side micro-frontends work with existing frameworks using concrete patterns: Astro.js server islands, Next.js multi-zones, and Module Federation for shared bundles. Draws on five years and roughly 100 teams helped, a four-decision composition framework (identify, compose, route, communicate), and real infra: CDN + TTLs, Lambda/container origins, memory HTML fragment caches (BBC) and a Formula 1 migration. Notes governance needs, prefers build-time pinned shared deps, and reports deployments jumping from ~2–3/month to ~25/day per team when sliced correctly.
AI-written summary · about
chapters (11)
- 0:00Micro-frontends and SSR challenges
- 1:11Micro-frontends vs components
- 8:15Four architecture decisions
- 9:20SSR composition techniques
- 13:14Formula 1 SSR case study
- 15:03Module Federation for SSR
- 17:31Server islands and Astro
- 21:26Developer experience in SSR
- 22:29SSR caching strategies
- 23:33Governance and observability
- 24:57Resources and closing
related talks
30mMicro Frontends in React — a State of the Art Approach
01h 13mArchitecting complex JavaScript setups for large scale enterprise projects
06mFramework Inception with Micro Frontend Composition
44mMicro Frontend Discovery
21mEmbracing Micro-frontends: A Comprehensive Guide for Modern Web Development
41mMicro-frontends: the golden circle
47mDemystifying Micro Frontends
46mScaling Micro-Frontends with Custom Elements