Powering up Micro-frontends at the Edge!
summary
Shows an actual migration path: break a legacy SPA into independently deployed fragments running on Cloudflare Workers, stream their responses into a parent page using fragment architecture and service bindings, and incrementally inject pieces via fragment piercing so login or feed load faster than the old monolith. Demos use Quick and SolidJS, load fragments from 270+ points of presence, and use an iframe trick for client-side context isolation to avoid DOM/ state bleed while keeping eager interactivity.
AI-written summary · about
chapters (10)
- 0:00Micro-frontends at the edge intro
- 2:18Monolithic frontend challenges
- 5:25What are micro-frontends
- 8:14Server-side with Cloudflare Workers
- 10:25Fragment architecture demo
- 13:57Incremental adoption
- 16:25Fragment piercing legacy
- 20:04Shared state isolation
- 23:38Edge micro-frontends benefits
- 25:24Resources and final thoughts
related talks
15mPowering up Micro-frontends at the Edge!
20mPowering Up Micro Frontends At The Edge!
30mSolving the micro-frontend puzzle with fragments architecture
33mSPAs, full-stack, micro-frontends, enterprise migrations, what the quack?
36mMicro Frontends - Breaking Monoliths
24mScaling Frontend Development using Micro-frontends
48mMicrofrontend Architecture – technical implementation.
45mMicro Frontends in Action!