Initial cache setup for auth information. - #1841
Open
MikeNeilson wants to merge 2 commits into
Open
Conversation
MikeNeilson
force-pushed
the
devops/cache-user-info
branch
from
July 16, 2026 17:28
a0303a6 to
a369ab9
Compare
MikeNeilson
force-pushed
the
devops/cache-user-info
branch
2 times, most recently
from
August 7, 2026 17:50
eb9331f to
ae9a53e
Compare
MikeNeilson
force-pushed
the
devops/cache-user-info
branch
2 times, most recently
from
August 20, 2026 22:24
84ed992 to
c941980
Compare
MikeNeilson
marked this pull request as ready for review
August 24, 2026 15:21
MikeNeilson
force-pushed
the
devops/cache-user-info
branch
from
August 24, 2026 15:21
c941980 to
546239b
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.
Summary
Reduce database load per request by caching DataPrincipal objects for some amount of time
before reloading from the database.
The TTL is "fixed", e.g. after the timeout the value is remove regardless of usage. This so that we don't over cache principal objects in case of removed credentials.
The LRU portion is so that the map object has bounded memory.
NOTE: I do not expect this to work well or be used for time series caching, that requires some more complexity.
Related Issue
No open issue
Validation
General usage within the API.
TODO:
caching does work, but some issues with behavior definitely indicate some specific formal tests are required. Will get to those eventually, and any comments about it welcome. Design commentary definitely welcome.
Checklist