liveBook · Manning

Partial hydration

As explained in Fast by Default

Islands architecture renders mostly static content without JavaScript and hydrates only isolated components that require interactivity.

Partial hydration uses an islands architecture to hydrate interactive components independently instead of blocking the page while everything becomes interactive. This reduces client-side hydration blocking and limits unnecessary code execution. section 5.2.1

Use partial hydration to distinguish static page content from interaction that requires client-side JavaScript:

  • Render available content progressively rather than waiting for all client-side work to finish. section 5.2.1
  • Hydrate interactive components independently, accepting the architectural constraint of organizing the page into islands. section 5.2.1

Rendering strategy comparison

All-at-once client-side rendering waits for all JavaScript before rendering, whereas an islands architecture hydrates components independently and avoids making the entire page wait for interactivity. section 5.2.1

Table 5.1 Web rendering approaches
Rendering approach
Category
Waits for
Trade-offs
Server-Side Rendering
All-at-once
All data before sending HTML
Response blocked by server’s slowest data source
Client-Side Rendering
All-at-once
All JavaScript before rendering
User sees blank screen or loading indicator
Streaming SSR
Progressive
Nothing; sends chunks as ready
Added complexity
Islands
Progressive
Nothing; hydrates components independently
Architectural constraints

Compare islands with server-side rendering, client-side rendering, and streaming SSR by their blocking behavior and trade-offs. section 5.2.1

How Fast by Default covers it

How deep it goes
Defines selective hydration and compares trade-offs, but stops short of implementation code or framework-specific setup.
Examples
Contrasts all-at-once rendering with independently hydrated components using a rendering comparison table and architecture figure.
What you can do after
Evaluate rendering trade-offs using hydration behavior, blocking characteristics, and architectural constraints.
How it connects
Connects islands architecture with progressive rendering, streaming SSR, server-side rendering, and client-side rendering.

Also explained in

Compare how 2 books explain partial hydration →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fast by Default. The section links point to the parts of the book it draws on.