Skip to content

Commit 9e00f71

Browse files
authored
Revise caching levels terminology in documentation
Updated caching level descriptions for clarity and consistency.
1 parent 62fa39b commit 9e00f71

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/AGentleIntroduction.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -65,8 +65,8 @@ Read more [**here**](CacheStampede.md), or enjoy the complete [**step by step**]
6565
There are 2 caching levels, transparently handled by FusionCache for us.
6666

6767
These are:
68-
- **1️⃣ Primary**: it's a memory cache, is always there and is used to have a very fast access to data in memory, with high data locality. We can give FusionCache any implementation of `IMemoryCache` or let FusionCache create one for us
69-
- **2️⃣ Secondary**: is an *optional* distributed cache (any implementation of `IDistributedCache` will work) and, since it's not strictly necessary and it serves the purpose of **easing a cold start** or **coordinating with other nodes**, it is treated differently than the primary one. This means that any potential error happening on this level (remember the [fallacies of distributed computing](https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing) ?) can be automatically handled by FusionCache to not impact the overall application, all while (optionally) logging any detail of it for further investigation
68+
- **1️⃣ L1**: it's a memory cache, is always there and is used to have a very fast in-memory access to frequently accessed data (hot data), with high data locality. We can give FusionCache any implementation of `IMemoryCache` or let it create one for us, automatically
69+
- **2️⃣ L2**: is an *optional* distributed cache (any implementation of `IDistributedCache` will work) and serves the purpose of **easing a cold start** or **sharing cached data** with other nodes/pods. It is treated differently than L1, meaning any potential error happening on this level (remember the [fallacies of distributed computing](https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing) ?) can be automatically handled by FusionCache to not impact the overall application, all while (optionally) logging any detail of it for further investigation
7070

7171
Everything is handled transparently for us.
7272

0 commit comments

Comments
 (0)