You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/AGentleIntroduction.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,7 +110,7 @@ As we know from the [Fallacies Of Distributed Computing](https://en.wikipedia.or
110
110
111
111
Without some extra care what can happen is that data would not be saved in the distributed cache or other nodes may not be notified of changes: this would result in out-of-sync issues.
112
112
113
-
wouldn't it be nice if FusionCache would help us is some way when transient error happens?
113
+
Wouldn't it be nice if FusionCache would help us is some way when transient error happens?
114
114
115
115
Enter **Auto-Recovery**: everything is done automatically, and it just works.
116
116
@@ -121,9 +121,9 @@ Read more [**here**](AutoRecovery.md).
121
121
122
122
Tagging is an incredibly powerful feature: cache entries can be tagged with one or more tags, and later they can be evicted all at once by just calling `RemoveByTag("my-tag")`.
123
123
124
-
The overall [design](https://github.com/ZiggyCreatures/FusionCache/issues/319) used to achieve this is such that, even when working against a massive cache with millions of entries, will not incur in any upfront cost (yes, even a distributed L2 like a Redis gigantic instance).
124
+
The overall [design](https://github.com/ZiggyCreatures/FusionCache/issues/319) used to achieve this is such that, even when working against a massive cache with millions of entries, will not incur in any upfront cost (yes, even with a gigantic distributed cache as L2, like a big Redis instance).
125
125
126
-
Tagging works in any supported scenario: with or without an optional L2 (distributed level), an optional backplane, shared caches, cache key prefix, fail-safe, soft/hard timeouts, auto-recovery and everything else.
126
+
Tagging works in any supported scenario: with only L1, with L1+L2, with or without an optional backplane, shared caches (both L1 and L2), cache key prefix, fail-safe, soft/hard timeouts, auto-recovery and everything else.
127
127
128
128
Read more [**here**](Tagging.md).
129
129
@@ -132,7 +132,9 @@ Read more [**here**](Tagging.md).
132
132
133
133
Thanks to the design used for the Tagging feature (see above), FusionCache also supports a proper `Clear()` mechanism for the entire cache.
134
134
135
-
Yes, yes: the abiltiy to clear seems like an easy one but when we consider things like shared caches, cache key prefix and all the other features... it's definitely not an easy feat. But yeah, it just works.
135
+
Yes, yes: the abiltiy to clear the cache seems like an easy one, but when we consider things like multiple levels, shared caches, cache key prefix and all the other features... it's definitely not an easy feat.
0 commit comments