Cache Stale-While-Revalidate Storms Flooding Downstream Origin Servers

Hardened Implementation Steps

1. 1Ingress Boundary Defense: Enable Origin Shielding (centralized parent caching tier) and configure request collapsing at the edge, ensuring exactly one background revalidation r
2. 2Failure Containment: Eliminate unconstrained buffering and propagate physical backpressure.
3. 3Invariant Enforcement: Pair edge stale-while-revalidate with Origin Shielding and request collapsing to prevent CDN origin floods.

Production Code Contrast & Implementation

// HARDENED: Singleflight mutex coalescing with probabilistic early refresh
public byte[] getProduct(String key) {
    // XFetch algorithm evaluates early background refresh before TTL expiration
    if (shouldProbabilisticEarlyRefresh(key, beta, delta)) {
        backgroundPool.submit(() -> refreshCacheKey(key));
    }
    // Singleflight ensures exactly ONE upstream DB fetch executes per in-flight key
    return singleflightGroup.execute(key, () -> database.queryProduct(key));
}

Alternatives Evaluated

• →Naive Approach: When an article goes viral (50,000 QPS), the edge serves the stale copy while triggering an origin revalidation. Because 50 distinct edge PoPs all tri
• →Production-Hardened Pattern: Enable Origin Shielding (centralized parent caching tier) and configure request collapsing at the edge, ensuring exactly one background revalidation r

Extension Implementation Steps

1. 1Track real-time latency gradients and inflight concurrency.
2. 2Reject excess traffic at the ingress boundary within <0.1ms.
3. 3Monitor P99 latency and verify autonomous recovery when downstream pressure subsides.

Follow-Up Trade-Offs

• ⚖Architectural Invariant: "Pair edge stale-while-revalidate with Origin Shielding and request collapsing to prevent CDN origin floods."
• ⚖Physical Resource Boundary: Dynamic admission control ensures worker threads never buffer dead requests during downstream brownouts.