Caching
posts (6)
- 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 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 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.
- series · 17 parts
Frontend Rendering: from server-side pages to hybrid rendering
A chronology of decisions about when, where and how the UI is produced: from a full document off the server to a composition of build, request, cache…