Skip to content

Clarify HybridCache stampede protection scope #55180

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
gewarren merged 2 commits into from
Jul 30, 2026
+2 −2
Merged

Clarify HybridCache stampede protection scope #55180

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8783d74
Clarify HybridCache stampede protection scope
svick Jul 29, 2026
0f3f882
Improve wording
svick Jul 29, 2026
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
4 changes: 2 additions & 2 deletions docs/core/extensions/caching.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Caching in .NET
description: Discover effective ways to implement in-memory and distributed caching in .NET. Boost app performance and scalability with .NET caching.
ms.date: 10/22/2025
ms.date: 07/28/2026
ai-usage: ai-assisted
---

Expand Down Expand Up @@ -253,7 +253,7 @@ The <xref:Microsoft.Extensions.Caching.Hybrid.HybridCache> library combines the
`HybridCache` offers several advantages over using `IMemoryCache` and `IDistributedCache` separately:

- **Two-level caching**: Automatically manages both in-memory (L1) and distributed (L2) cache layers. Data is retrieved from in-memory cache first for speed, then from distributed cache if needed, and finally from the source.
- **Stampede protection**: Prevents multiple concurrent requests from executing the same expensive operation. Only one request fetches the data while others wait for the result.
- **Stampede protection**: Prevents multiple concurrent requests that use the same `HybridCache` instance from executing the same expensive operation. Only one request fetches the data while others wait for the result. This coordination doesn't extend to other `HybridCache` instances, even if they use the same distributed cache.
- **Configurable serialization**: Supports multiple serialization formats including JSON (default), protobuf, and XML.
- **Tag-based invalidation**: Groups related cache entries with tags for efficient batch invalidation.
- **Simplified API**: The `GetOrCreateAsync` method handles cache misses, serialization, and storage automatically.
Expand Down
Loading