feat: add Redis-backed cache proxy for search and resolver endpoints#805
Draft
thostetler wants to merge 1 commit intoadsabs:masterfrom
Draft
feat: add Redis-backed cache proxy for search and resolver endpoints#805thostetler wants to merge 1 commit intoadsabs:masterfrom
thostetler wants to merge 1 commit intoadsabs:masterfrom
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #805 +/- ##
========================================
+ Coverage 61.6% 61.6% +0.1%
========================================
Files 312 315 +3
Lines 36000 36320 +320
Branches 1594 1649 +55
========================================
+ Hits 22148 22355 +207
- Misses 13815 13927 +112
- Partials 37 38 +1
🚀 New features to boost your workflow:
|
cda6998 to
d60b340
Compare
Adds a server-side cache proxy that stores upstream API responses in Redis for configurable TTLs. Client-side search and resolver requests route through the proxy. Abstract SSR uses the same cache layer. Includes origin validation, rate limiting, cache status headers, and a dev-only hit/miss indicator.
d60b340 to
8f24b3a
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
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.
Client-side search and resolver requests were hitting the upstream API
directly on every page load with no server-side caching layer. This
adds a Redis-backed cache proxy that sits between the browser and the
upstream Solr/resolver APIs.