Comparison
Incremental static regenerationvsStatic site generation
Incremental static regeneration
the page is served from the last build, and the first visitor after the timer expires triggers a fresh one in the background.
Static generation with a revalidation window: pages are served from cache, and after a set age the next request serves the stale copy while a rebuild happens behind it. It buys most of static's speed for content that changes on a schedule, without rebuilding the whole site. The catch is that someone always sees the stale version, and reasoning about which version a given visitor got becomes genuinely hard during an incident.
Full entry →Static site generation
every page was rendered once at build time and the server is just handing out files.
Rendering every page during the build and serving the results as static files from a CDN. It is the fastest and cheapest option and the one with the fewest moving parts at runtime. It breaks down when the content changes often or depends on who is asking, because the only way to update a page is to rebuild it, and build time grows with the number of pages.
Full entry →