Hydration Islands Streaming and Resumability
summary
Compares concrete implementations and tradeoffs: Astro: zero JavaScript by default and islands hydrate per-component, Marko (since 2014) uses streaming SSR plus automatic partial hydration, and Vercel reports measurable Core Web Vitals gains from selective hydration. Describes resumability as Qwik’s model where server-executed state and event handlers are serialized and Qwik resumability: lazy event handlers resume on demand to avoid client redoing work, with resumability operating at subcomponent granularity rather than whole-island level.
AI-written summary · about
chapters (14)
- 0:00Introduction and overview
- 1:52Evolution of rendering strategies
- 4:40What is hydration?
- 7:11Islands architecture explained
- 9:59Frameworks using Islands
- 11:45What is resumability?
- 13:12Resumability vs traditional hydration
- 16:20React 18 hydration improvements
- 18:50React Server Components
- 21:19Benefits of Server Components
- 22:43Future of rendering patterns
- 25:34Closing thoughts and patterns
- 28:26Historical context and cycles
- 31:16Key takeaways and Q&A
related talks
35mHydration, Islands, Streaming, Resumability... Me, Oh My!
21mHydration, Islands, Streaming, Resumability… Oh My!
49mQwik: Streaming JavaScript framework
30mUsing Qwik To Turn React Application Into Lazy Hydration Islands
40mThe digital age of hydration: understanding types of hydration for web use
21mQwik: web revolution by default
49mJavaScript Streaming - A Qwik glimpse into the future
48mResumability in the next generation frontend framework With O(1) loading time