liveBook · Manning

Stream processing

As explained in Fast by Default

Streaming server-side rendering sends rendered HTML incrementally as data and page sections become available.

Streaming server-side rendering sends HTML in chunks as page sections become ready, allowing the browser to display available content without waiting for the slowest data source. section 5.2.1

Streaming SSR addresses the blocking behavior of all-at-once rendering:

  • Traditional SSR waits for every data request and the complete HTML response. section 5.2.1
  • Streaming sends ready sections immediately, reducing the delay before visible content appears. section 5.2.1
  • Streaming SSR addresses server blocking, while Islands architecture addresses client-side hydration blocking. section 5.2.1

Product page with inventory and reviews

A product page can display available content while inventory and reviews arrive separately instead of waiting for both services. Equivalent pages measured with Nordnet showed 32% lower Time to First Byte and 40% better Total Blocking Time. 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 Streaming SSR with all-at-once server-side rendering, client-side rendering, and Islands architecture. section 5.2.1

How Fast by Default covers it

How deep it goes
Explains the blocking pattern, incremental response behavior, framework interfaces, and measured outcomes without detailing production safeguards.
Examples
Uses product pages with inventory and reviews, Nordnet measurements, and React streaming APIs as concrete examples.
What it assumes
Understand all-at-once server-side rendering, client-side rendering, data fetching, and client-side hydration blocking.
What you can do after
Apply streaming SSR through React 18 renderToPipeableStream, renderToReadableStream, or framework-provided Suspense boundaries.
How it connects
Connects streaming SSR with server-side rendering, client-side rendering, Islands architecture, hydration, and Suspense boundaries.

Also explained in

Compare how 25 books explain stream processing →

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.