perf: cache GET /api/items on the Cloudflare edge#7
Merged
Conversation
|
🔎 Cloudflare preview: https://c0a93ba5-feedreader.phatpham9.workers.dev Uploaded from |
Same pattern as the AI personalization ranking cache: a synthetic GET request as the Cache API key, with latestSuccessAt baked in so entries auto-invalidate on each source refresh (no manual purge), plus a 6h TTL backstop. Unlike personalize there's no LLM call to spare — the full JSON response is cached as-is, sparing D1 the same paginated read on every repeat poll of a given (source filter, query, page). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
phatpham9
force-pushed
the
feature/cache-items-api
branch
from
6b56756 to
0638252
Compare
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
1 participant
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.
Same pattern as the AI personalization ranking cache: a synthetic GET request as the Cache API key, with latestSuccessAt baked in so entries auto-invalidate on each source refresh (no manual purge), plus a 6h TTL backstop. Unlike personalize there's no LLM call to spare — the full JSON response is cached as-is, sparing D1 the same paginated read on every repeat poll of a given (source filter, query, page).