QA
summary
Claims and concrete tradeoffs: islands are independent UI pieces that hydrate on demand, so there is no fixed sensible limit though lots of interacting widgets push a move to SPA; incremental static regeneration and deferred generation work but ISR is host‑specific and complicates frameworks; static sites scale to tens of thousands (80,000) pages with builds taking around five to ten minutes at extreme scale; using MDX can mean bundling hundreds of thousands of JS files which slows generation; image optimization supports remote URLs and SSG or SSR.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:43Islands per page vs SPA
- 2:31ISR DSG and framework complexity
- 4:58Scalability of Astro
- 6:44Astro image component
- 7:28Angular and web components in Astro
- 8:34Client-side visibility and hydration
- 9:38Suspense in Astro
- 10:21Astro account settings
- 11:23Markdown alternatives
related talks
21mHydration, Islands, Streaming, Resumability… Oh My!
22mAdvanced Site Rendering Patterns on the Jamstack
28mSingle Page Applications - was it a good idea?
33mSPAs, full-stack, micro-frontends, enterprise migrations, what the quack?
24mThe Performance Aspect of Building and Deploying Static Sites
30mRendering Revealed
35mHydration, Islands, Streaming, Resumability... Me, Oh My!
29mA New Paradigm: How Do I Optimally Break my UI Into Queries?