Hundreds of components, hundreds of experiments and only one page
summary
A frontend architecture that turns a monolithic 15 MB/37.5k-file page into per-feature bundles so the largest delivered page is ~300 KB and many requests are ~100 KB. The backend sends a JSON layout; a registry maps feature types to adapters that convert props and return SSR HTML, with each feature compiled into its own chunk and isolated experiment folders. The system swaps platform-specific files at build time and uses progressive SSR with partial hydration to hydrate only interactive nodes.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:13Page as app
- 6:50Component and bundle separation
- 9:59Routing across platforms
- 14:15Registry and experiments
- 17:28Page load optimization
- 21:48Q&A
related talks
31mFaster content websites via SSR and progressive hydration of Web Components
41mHigh-Performance Web UI with Web Components
38mBreak Up With Your Frontend Monolith
47mThe Micro Frontend Architecture: How to Turn Your Website into a Giant Collaborative Puzzle
40mThe state of frontend frameworks in 2023
31mBack to boring
30mThe Recipe For Scalable Frontends
37mData-Driven Frontend Components and the New Jira Navigation