Composable decoupled frontends: the Jamstack and beyond
summary
Argues for an API-first design that splits UI by vertical use cases, using API gateways, edge/origin functions and server-side composition to keep frontends tiny and fast; cites Jamstack 2022 usage (45% personal sites, 17% other) and that only 28% of global users browse on iPhone, so heavy JS raises bounce rates by 32–90%. Reports three years of experiments with module federation (Webpack 5) that work but demand strict governance. Recommends HTML-first frameworks like Astro, Qwik, Fresh, Enhanced and performance budgets (≤50 requests, ≤3 MB).
AI-written summary · about
chapters (19)
- 0:00Introduction to talk
- 1:05Jamstack evolution and impact
- 3:16Why decouple monolithic systems
- 5:27Decoupling strategies and infrastructure
- 8:58API-first design approach
- 11:23Rethinking micro frontends
- 13:34Decoupled composable frontends
- 14:39Development cycle and user experience
- 17:34Designing for diverse users
- 21:50Performance budgets and user constraints
- 22:51Composing decoupled frontends
- 24:37Vertical vs horizontal splits
- 27:10Module Federation and governance
- 29:39JavaScript optimization principles
- 31:05Modern rendering patterns
- 34:17Server-side execution and edge functions
- 36:30Future of frontends and APIs
- 39:02Summary and key takeaways
- 40:48Q&A session
related talks
35mThe Rise of JAMStack
31mThe post-Jamstack world and the rise of Hybrid Frameworks
41mLow-budget JavaScript: composable frontends that are fun and friendly
30mRise of the Jamstack — Mathias Biilmann
27mThe Post Jamstack World & the Rise of Hybrid Frameworks
30mMicro Frontends in React — a State of the Art Approach
34mMicro Frontends
29mQuo vadis, frontend?