Performance
posts (15)
- 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 rendering14/17
Islands architecture: interactive fragments in a mostly static document
The starting point stops being the application. The page is a document, and only the fragments that truly need a client runtime get one.
- Frontend Rendering: from server-side pages to hybrid rendering13/17
Selective and progressive hydration: not everything deserves CPU now
Hydration stops being one startup task. Client CPU becomes a resource allocated by priority and by the user's real intent.
- 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 rendering9/17
Revalidation and ISR: static output that expires
ISR is not a separate rendering category but a cache with controlled inconsistency: precomputed HTML, expiration and regeneration.
- 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.