4 ms·
There are thousands (millions? billions?) of websites that are not replicated, do not use a CDN, have no multiple locations. When you rebuild the site due to s
by PaulDavisThe1st 7y ago
There are thousands (millions? billions?) of websites that are not replicated, do not use a CDN, have no multiple locations.
When you rebuild the site due to some change, you are updating one single folder heirarchy on one server somewhere. No caching. Just build (and if necessary as a separate step, copy/install).
I didn't not see anywhere in his writeup that suggest that you generate pages based on requests.
- chrismorgan 7y agoIf you are modifying HTML directly, no cache is involved. But if you are modifying something that is used to generate the HTML, what you deploy is a complete cache of the operation of building the site. The fact that you could throw it away and build a new version is what makes it match the definition—just because no piece is colloquially known as a cache doesn’t stop it from being just that. Build artefacts are a cache of the operation of compiling the source. To demonstrate this, putting the “requests” part into it: imagine hooking the static site generator up to the server directly, so that a request to /widgets.html turned into “run the static site generator, but only ask it for what it would output for /widgets.html, then respond with that”. The terminology I used is quite correct and widespread in the industry at large—it’s just that it’s not at all in vogue in the JAMstack world.