Performance
posts (22)
- 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.
- Ways of Talking to a Backend: From HTML Forms to GraphQL6/6
GraphQL: Letting the Client Define the Shape of Data
The response stops belonging to a resource or an operation and starts belonging to the client's query. Flexibility is paid for with predictable execution and…
- 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.
- Frontend Rendering: from server-side pages to hybrid rendering7/17
SSG: rendering before the user exists
Build-time rendering trades request cost for build cost. You pay once, serve cheaply, and start having a data freshness problem.
- 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.