Edge caching
Edge caching stores ready-made copies of pages and files in data centres close to visitors, so most requests are answered without rebuilding anything.
The “edge” is the outer layer of a CDN, the servers nearest the visitor. When a page is cached there, the visitor gets it in milliseconds, and the server behind it never has to run.
The hard part is invalidation: making sure visitors see the new version as soon as something changes. Good setups tie the cache to content versions, so a publish makes the old copies irrelevant at once.
How Regular approaches it
In Standard, each publish in the CMS rotates a revision key. Rendered pages are cached in Cloudflare's edge cache and in R2 storage under that key, so the first visitor after a publish gets a freshly rendered page and everyone after that gets the cached one. No rebuilds, no stale pages.
Sources and further reading
- Cloudflare Cache documentationdevelopers.cloudflare.com
- HTTP caching, MDN Web Docsdeveloper.mozilla.org