feat(backend): Redis caching for frequently accessed data - #696
Open
woahwhattheheck wants to merge 8 commits into
Open
woahwhattheheck wants to merge 8 commits into
woahwhattheheck wants to merge 8 commits into
Conversation
Reference the ForecastController-owned Redis client explicitly in the two unbound settings handlers. This keeps GET from failing before configuration loading and PUT from reporting a receiver error after saving without invalidating the cache. Continues the existing PayD Protocol-Guild#696 / Protocol-Guild#533 submission and preserves its original implementation and publication credit. Static source and actual route registration inspected; no runtime, compiler, test, workflow or deployment execution was performed for this correction.
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.
Closes #533.
What
Caches hot reads (employee service, forecasting/fx rates, forecast controller) through the existing Redis client with bounded TTLs; invalidates on writes.