stale-while-revalidate¶
stale-while-revalidate.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Cache TTL Refresh
- Instead the edge refreshes asynchronously: once an entry is inside the last sliver of its TTL, or on the first request after expiry, it serves the still-fresh copy immediately and re-fetches in the background — stale-while-revalidate.
This sourceIt is the standard way to refresh before the cold miss is felt, which is why it anchors the example above.
- Instead the edge refreshes asynchronously: once an entry is inside the last sliver of its TTL, or on the first request after expiry, it serves the still-fresh copy immediately and re-fetches in the background — stale-while-revalidate.
- Resolver Cache with TTL
- … crucially, it applies a stale-while-revalidate discipline — it keeps serving the cached endpoint while the refresh is in flight, so a slow network never stalls the app, and if the source is briefly unreachable it serves the last-known-good answer under a stale-if-error grace rather than failing outright.
This sourceThey are the standard way a caller-side cache trades a bounded risk of staleness for responsiveness and resilience.
- … crucially, it applies a stale-while-revalidate discipline — it keeps serving the cached endpoint while the refresh is in flight, so a slow network never stalls the app, and if the source is briefly unreachable it serves the last-known-good answer under a stale-if-error grace rather than failing outright.
- Web Cache
- The discipline: mark user-specific responses `private`/`no-store`, set `Vary` correctly so variants do not collide, and use stale-while-revalidate
This sourceIt trades a small, bounded window of staleness for lower latency and protection of the origin from expiry stampedes.
- The discipline: mark user-specific responses `private`/`no-store`, set `Vary` correctly so variants do not collide, and use stale-while-revalidate
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:96a6ea09f131 · see in the full table