SSR
posts (11)
- Frontend Rendering: from server-side pages to hybrid rendering17/17
Modern rendering is composition
Rendering stopped being a single stage. It is the placement of work across time, space and runtimes, and the framework is a consequence of those decisions.
- Frontend Rendering: from server-side pages to hybrid rendering16/17
Server Components: moving the execution boundary
The rendering boundary stops running through the page and starts running through the module graph. Some components never have a client-side implementation.
- Frontend Rendering: from server-side pages to hybrid rendering15/17
Resumability: what if we don't hydrate at all?
The server records enough information that the client never rebuilds the component tree. Code loads because execution became necessary.
- Frontend Rendering: from server-side pages to hybrid rendering12/17
Edge rendering: compute moved closer to the user
Moving compute closer to the user only pays off when the data travels with it. Otherwise we shorten one hop and lengthen the rest.
- Frontend Rendering: from server-side pages to hybrid rendering11/17
Partial Prerendering: one page, several clocks
The route stops being the unit of decision. A static shell is produced earlier, dynamic fragments arrive at request time or through the stream.
- Frontend Rendering: from server-side pages to hybrid rendering10/17
Streaming SSR: stop waiting for the whole tree
The response stops being atomic. The server sends finished fragments and the slowest dependency no longer blocks the entire document.
- Frontend Rendering: from server-side pages to hybrid rendering8/17
Deferred generation: don't build what nobody requests
The request stops being the moment of rendering and becomes a trigger for materialising an artifact. The first user pays, everyone after gets a file.
- Frontend Rendering: from server-side pages to hybrid rendering6/17
Hydration: connecting HTML with a working application
The server sends the result of rendering, not the application. The browser has to rebuild the component tree and wire it to the existing DOM.
- Frontend Rendering: from server-side pages to hybrid rendering5/17
SSR returns: the server renders HTML again
The server renders the first view not to make the frontend disappear, but to make content exist earlier. The rest of the cost stays on the client.
- Frontend Rendering: from server-side pages to hybrid rendering1/17
Server-rendered web: before the frontend became an application
The server assembled a full document for every request and the browser was a document renderer. A simple model, as long as the whole document could be the unit…