Cache external display metadata with explicit freshness #40
Labels
No labels
area/backend
area/frontend
area/tooling
kind
build
kind
chore
kind
ci
kind
docs
kind
feat
kind
perf
kind
test
size
l
size
m
size
s
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#37 Attribute groups to registered and unregistered authors
viacheslavshuka/quorum
#38 Link reusable groups to tournaments without duplicating testing history
viacheslavshuka/quorum
Reference
viacheslavshuka/quorum#40
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
External tournament display and search requests can reuse stale-tolerant metadata. Identity verification must still establish the current external profile state.
Scope
Add bounded caching to the rating-data adapter's display and search reads. Choose and document lifetimes, invalidation, and failure behavior. Do not introduce Redis or unrelated statistics precomputation.
Acceptance criteria
Validation
Use a controlled upstream adapter and clock to check hit, miss, expiry, changed external data, upstream failure, and concurrent refresh. Demonstrate that a cached old verification marker cannot satisfy a new identity check.
Dependencies
Related work