Service Worker Stale-While-Revalidate

By Michael Samuel Naeem · June 15, 2026 · 7 min read

PerformancePWACaching

Stale-while-revalidate served a week-old pricing page from cache while sales ran a promotion — users saw wrong prices until hard refresh.

The question behind the ticket

Production engineering for service worker stale-while-revalidate with freshness bounds. Review 1: teams that treat service worker stale-while-revalidate with freshness bounds as a checklist item usually rediscover the same incident quarterly. Name an owner, define a leading metric, and schedule a 15-minute review after the next traffic doubling — assumptions age faster than code.

Answer with nuance

Production engineering for service worker stale-while-revalidate with freshness bounds. Review 2: teams that treat service worker stale-while-revalidate with freshness bounds as a checklist item usually rediscover the same incident quarterly. Name an owner, define a leading metric, and schedule a 15-minute review after the next traffic doubling — assumptions age faster than code.

Implementation walkthrough

        Ship the smallest vertical slice first — one route, one widget, one webhook endpoint — with rollback documented before expanding scope. Unbounded SWR without max-age, version headers, or skipWaiting coordination That mistake is expensive because it only surfaces under real traffic mixes.

        ```typescript
        const worker = new Worker(new URL("./compute.worker.ts", import.meta.url), { type: "module" });

const buffer = new ArrayBuffer(1024 * 1024); worker.postMessage({ type: "process", buffer }, [buffer]); worker.onmessage = (e) => updateUI(e.data); ```

        Wire metrics at the same time as the feature. If you cannot answer "did this make users faster or safer?" within a week of launch, the change is not finished.

Security angle

Frontend and backend changes share an attack surface. Treat user content, URL parameters, and webhook bodies as hostile input. Prefer fail-closed verification, short-lived credentials, and constant-time comparisons for crypto.

Content Security Policy, Subresource Integrity, and Trusted Types stack for DOM XSS defense. Security work without tests regresses — add CI checks that fail on unsafe patterns.

Testing beyond happy path

Production engineering for service worker stale-while-revalidate with freshness bounds. Review 5: teams that treat service worker stale-while-revalidate with freshness bounds as a checklist item usually rediscover the same incident quarterly. Name an owner, define a leading metric, and schedule a 15-minute review after the next traffic doubling — assumptions age faster than code.

Day-two operations

Production engineering for service worker stale-while-revalidate with freshness bounds. Review 6: teams that treat service worker stale-while-revalidate with freshness bounds as a checklist item usually rediscover the same incident quarterly. Name an owner, define a leading metric, and schedule a 15-minute review after the next traffic doubling — assumptions age faster than code.

What I'd ship this week

Stale-while-revalidate served a week-old pricing page from cache while sales ran a promotion. If I were prioritizing one action this sprint: pick the single user journey where service worker stale-while-revalidate with freshness bounds hurts most, instrument it, fix the invariant, and only then generalize.

Performance and reliability work compounds when tied to business metrics — conversion, support volume, integration churn — not abstract Lighthouse scores alone.

Coordination with backend and platform

Service Worker Stale-While-Revalidate With Freshness Bounds rarely lives entirely in the browser or client. Align cache TTLs, API error shapes, and deploy windows with the teams owning those systems — otherwise you optimize one layer while another invalidates gains.