Keeping It Simple
summary
Claims a concrete architecture called distributed persistent rendering and shows prototypes that run critical pages at build time while generating and persisting the rest on demand. It evaluates trade-offs: longer build times for huge catalogs, costs of client-side rendering, and why stale-while-revalidate breaks predictability. Promises preserved atomic deploys and a predictable URL state, offers RFC and prototypes to test whether the approach actually scales and reduces developer complexity.
AI-written summary · about
chapters (4)
- 0:00Start
- 2:34do you know. what a user will experience for a given state?
- 5:38what a user will experience at a given URL?
- 5:51what happens if I push deploy preview #110 right now?
related talks
20mAdvanced Rendering Patterns
33mRendering on the Web: Performance Implications of Application Architecture
21mImplementation and use cases of modern rendering patterns
41mGetting to the glass - approaches to rendering views on the web
22mAdvanced Site Rendering Patterns on the Jamstack
29mDesigning very large JavaScript applications
52mGetting to the Glass
43mFine-grained everything