docs: minimal Workers Cache adoption plan (Chapter 14)#47
Draft
scottmessinger wants to merge 2 commits into
Draft
docs: minimal Workers Cache adoption plan (Chapter 14)#47scottmessinger wants to merge 2 commits into
scottmessinger wants to merge 2 commits into
Conversation
Replaces the over-scoped re-architecture proposal from PR #46 with the minimal adoption scope: enable native Workers Cache, move the custom domain onto the worker, delete the nginx dummy origin. No auth, protocol, or code changes. Key correction vs the earlier proposal/handoff: Workers Cache bypasses on inbound Authorization headers regardless of Cache-Control: public (unlike the zone CDN today), so auth-required stream reads BYPASS the native cache and the internal edge-cache/coalesce middleware becomes the load-bearing collapsing layer for them — it must be kept, not removed as redundant. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WBPrsDvrFACta2rq8qGLVF
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
durable-streams-demo-draw | 9d989a6 | Commit Preview URL Branch Preview URL |
Jul 08 2026, 09:17 PM |
…napshot The pkg.pr.new tarball for @cloudflare/vitest-pool-workers@11632 was republished with different content, so pnpm install --frozen-lockfile failed with ERR_PNPM_TARBALL_INTEGRITY on every CI job (also red on PR #46). Update the lockfile to the checksum the registry now serves. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WBPrsDvrFACta2rq8qGLVF
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
docs/14-workers-cache-adoption.md(+ index link): the minimal-scope plan for adopting Cloudflare's July 2026 Workers Cache. Docs only; no code changes.This replaces the over-scoped re-architecture proposal in #46 (gateway split, frame-addressed reads) — none of that is required to adopt the feature. The actual change is four steps: bump wrangler to ≥ 4.69.0, add
[cache] enabled = true, move the custom domain onto the worker, deletepackages/proxy+ the EKS deployment.The one correction that matters
The earlier proposal's handoff concluded the auth question was "resolved — no change needed" because the
rkreader key is in the cache key. That misses how the requests actually look: auth-required reads carryAuthorization: Bearer <JWT>(therkis never validated; JWT is the single auth source, per Chapter 12).Cache-Control: publicoverrides the Authorization rule (RFC 9111 §3.5 / Cloudflare Origin Cache Control). Chapter 7's loadtests confirm it: identicalBearertokens on every request, 98–99% HIT.publicdirective can matter — per Cloudflare's own docs, "nothing will ever be stored."So after migration, private-stream reads BYPASS the native cache and the worker's internal
caches.default+inFlightcoalescing becomes the load-bearing collapsing layer for them. The doc's main prescription: keep that middleware — it is not redundant cleanup. Public streams get native-cache collapsing in front (plus tiered caching), same as the zone CDN today.The doc also records a staging go/no-go checklist (collapsing parity, private-read BYPASS absorption, SSE lock behavior, cold-cache-per-deploy) and defers the Cloudflare-documented gateway/
ctx.exportssplit as an optional later enhancement.🤖 Generated with Claude Code
https://claude.ai/code/session_01WBPrsDvrFACta2rq8qGLVF
Generated by Claude Code