Skip to content

docs(glossary): describe the hydrating cache without comparing it to another library (2.1) #298

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

Closed
cosmin-staicu wants to merge 1 commit into from
Closed

docs(glossary): describe the hydrating cache without comparing it to another library (2.1) #298

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
2 changes: 1 addition & 1 deletion docs/reference/glossary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Alphabetical lookup for terms used across the docs.

**Hash tag** — A `{...}` substring inside a Redis key that pins the key to a single shard in Redis Cluster. Used by the sharded Pub/Sub strategy so the doorbell channel and the stream key collide on the same slot.

**Hydrating cache** — Proactive background refresh of a cache entry before it expires. Configured via `CachePolicy.RehydrateEnabled` + `RehydrateOptions`. Distinct from FusionCache's fail-safe — no stale data is ever returned. See [how-to/resilience.md](../how-to/resilience.md#hydrating-cache).
**Hydrating cache** — Proactive background refresh of a cache entry before it expires. Configured via `CachePolicy.RehydrateEnabled` + `RehydrateOptions`. It never returns stale data. See [how-to/resilience.md](../how-to/resilience.md#hydrating-cache).

**Jitter** — Uniform random delay added to L2 TTL at write time (`CachePolicy.JitterMaxDuration`) to spread cluster-wide expirations after bulk writes.

Expand Down
Loading