Skip to content

Commit 6b571b5

Browse files
Apply suggestions from code review
1 parent a359f91 commit 6b571b5

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

17/umbraco-cms/SUMMARY.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,7 @@
4545
* [Umbraco in Load Balanced Environments](fundamentals/setup/server-setup/load-balancing/README.md)
4646
* [Load Balancing Azure Web Apps](fundamentals/setup/server-setup/load-balancing/azure-web-apps.md)
4747
* [Load Balancing the Backoffice](fundamentals/setup/server-setup/load-balancing/load-balancing-backoffice.md)
48+
* [SignalR In Load Balanced Environments](fundamentals/setup/server-setup/load-balancing/signalR-in-backoffice-load-balanced-environment.md)
4849
* [Standalone File System](fundamentals/setup/server-setup/load-balancing/file-system-replication.md)
4950
* [Advanced Techniques With Flexible Load Balancing](fundamentals/setup/server-setup/load-balancing/flexible-advanced.md)
5051
* [Logging With Load Balancing](fundamentals/setup/server-setup/load-balancing/logging.md)

17/umbraco-cms/fundamentals/setup/server-setup/load-balancing/load-balancing-backoffice.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,9 @@ umbracoBuilder.SetServerRegistrar(new StaticServerAccessor());
2525

2626
This will ensure that all servers are treated as backoffice servers.
2727

28-
## Load balancing Isolated Caches
28+
## Load balancing Repository Caches
2929

30-
One of the issues with load balancing the backoffice is that all servers will have their own isolated caches. This means that if you make a change on one server, it won't be reflected on the other servers until their cache expires.
30+
One of the issues with load balancing the backoffice is that all servers will have their own repository caches. This means that if you make a change on one server, it won't be reflected on the other servers until their cache expires.
3131

3232
To solve this issue, a cache versioning mechanism is used. This is similar to optimistic concurrency control. Each server has a version number for its cache. When a server makes a change, it updates the version identifier. The other servers can then check the version identifier before accessing the cache. If the cache is out of date, they invalidate it.
3333

0 commit comments

Comments
 (0)