Skip to content

Commit db8108d

Browse files
authored
Fix typo in Backplane documentation
1 parent 7587dca commit db8108d

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

docs/Backplane.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ FusionCache will of course update both the L1 (memory cache) and the L2 (distrib
3131

3232
</div>
3333

34-
But... since the code (both our app code and FusionCache code) runs on the node that updated the entry, only the L1 where the update has been executed will be update.
34+
But... since the code (both our app code and FusionCache code) runs on the node that updated the entry, only the L1 where the update has been executed will be updated.
3535

3636
And what happens if the other nodes already had that entry cached? This happens:
3737

@@ -45,6 +45,10 @@ Basically the cache as a whole becomes **incoherent**, because depending on the
4545

4646
And this will last until the `Duration` elapses, and expiration occurs, on all those other nodes.
4747

48+
Is there a solution to this?
49+
50+
## 📢 Use a backplane
51+
4852
Luckily, there's an easy solution to this synchronization problem: we can use a **backplane**.
4953

5054
<div align="center">

0 commit comments

Comments
 (0)