Skip to content

chore: add documentation of caching + expiration #600

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tstirrat15 merged 1 commit into from
Oct 7, 2026
Merged

chore: add documentation of caching + expiration #600

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions app/spicedb/concepts/expiring-relationships/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,6 +125,14 @@ the datastore chosen.
deployments.
</Callout>

## Expiration and Caching

If a relationship expires during a cache window and SpiceDB has already cached a subproblem that uses that relationship,
if the cache window is valid for a given request,
SpiceDB will respond with the cached value even if a fresh datastore read would exclude that relationship.
This is a deliberate decision consistent with the rest of our caching semantics; if a given request
should not use a cached value, the `fully_consistent` consistency option can be used.

## Migrating Off Of Expiration With Caveats

If you implemented expiration using caveats, this section describes migrating to the new expiration feature.
Expand Down
Loading