Streaming SSR & Progressive Flushing vs Resumability vs Hydration
Streaming SSR still hydrates streamed HTML on the client, whereas resumability serializes listener boundaries to skip eager hydration.
Structured Comparison Matrix
| Dimension | Streaming SSR & Progressive Flushing | Resumability vs Hydration |
|---|---|---|
| Mental Model | Streams the HTML <head> and shell immediately over HTTP/2+ while slow backend queries run, then flushes deferred <template> chunks for out-of-order DOM replacement. | Contrasts eager SSR hydration—which replays component trees on the client to attach listeners—with resumability, which serializes state in HTML and loads handlers lazily. |
| Maturity & Domain | Baseline · Widely · Network & Performance Chrome 43+ · Firefox 65+ · Safari 10.1+ | Experimental · State & Architecture Chrome 1+ (HTML/JS runtime pattern) · Firefox 1+ (HTML/JS runtime pattern) · Safari 1+ (HTML/JS runtime pattern) |
| Prerequisites | ||
| When Not to Use | When not to use Streaming SSR: On static or edge-cached pages that render in under 15 ms, full-response caching with s-maxage is simpler and avoids open long-lived connections; if client hydration cost dominates, compare against Resumability vs Hydration. | When not to use Resumability: In dense, always-interactive single-page tools (Figma-like canvases, IDE editors) where 95% of UI handlers are needed within the first second anyway. |
Engine Mechanics & Trade-Offs
Flushes the HTML <head> and shell immediately over HTTP/2+ while slow data queries resolve, then streams deferred <template> chunks + inline swap scripts.
Key Pitfalls: Proxy buffering eating your stream: Reverse proxies (Nginx, misconfigured CDNs, or synchronous compression) often buffer the first 4–64 KB before forwarding, defeating Streams API Backpressure and turning streaming back into buffered SSR. Locked HTTP 200 status codes: Once the <head> flushes, you cannot retroactively s
Eliminates eager O(N) hydration boot by serializing framework state into HTML and lazily loading only the clicked handler's JS chunk via event delegation.
Key Pitfalls: Hydration mismatch cascades: Rendering Date.now() or window.matchMedia during SSR causes client hydration to throw away the server DOM and repaint from scratch. Uncached lazy chunks on slow 3G: Resumability trades boot JS for interaction-time chunk fetches; prefetch probable handlers via a Service Worker or <link rel="