SPAs, full-stack, micro-frontends, enterprise migrations, what the quack?
summary
A concrete claim and a working demo not a marketing rant Web Fragments let a legacy Angular SPA migrate incrementally by carving out UI parts into independently deployed fragments that use shadow roots to encapsulate CSS and separate JavaScript contexts so code can be unloaded and memory leaks reclaimed The team rebuilds the catalog as server rendered Analog and the cart in Qwik communicates via BroadcastChannel and shows a 2 second pause gone in the demo Cloudflare Dash runs this approach at scale with about 3,000 SLOC of orchestrator code and an expected ~100 fragments in the migration and it materially improves LCP and boot time
AI-written summary · about
chapters (12)
- 0:00Introduction
- 4:57Frontend tech choices
- 7:48Enterprise frontend migrations
- 10:56Iframes vs modern UIs
- 13:02Web Fragments intro
- 16:57Live demo: Web Fragments
- 22:15Encapsulated fragments benefits
- 25:26Faster rendering with Web Fragments
- 27:54Cloudflare production example
- 29:19Web Fragments advantages
- 31:26Web Fragments open source
- 32:52Q&A
related talks
33mPowering up Micro-frontends at the Edge!
29mSPAs are dead. Long live Microfrontends.
47mCamel and Eye of a Needle: Integration Approaches for SPA-based Micro Frontends
30mSolving the micro-frontend puzzle with fragments architecture
24mScaling Frontend Development using Micro-frontends
32mFrom Monolith to Micro Frontend
45mSPA, isomorphic and back to the server: our journey with JS
30mThe Recipe For Scalable Frontends