From d5705a9647335262b50bf4b603808cd73897245c Mon Sep 17 00:00:00 2001 From: Max Kotliar Date: Wed, 5 Nov 2025 21:09:19 +0200 Subject: [PATCH] docs/guides: use canonical link --- docs/guides/vm-architectures/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/vm-architectures/README.md b/docs/guides/vm-architectures/README.md index 75d84fb4d3..ec4841e1ad 100644 --- a/docs/guides/vm-architectures/README.md +++ b/docs/guides/vm-architectures/README.md @@ -21,7 +21,7 @@ The scope of the failure you are designing for is your **"blast radius".** Befor It is also crucial to distinguish between two fundamental goals: -* **Resilience (or Availability)** is about surviving failures. We achieve it by creating copies ([replicas](https://docs.victoriametrics.com/cluster-victoriametrics/#replication-and-data-safety)) of our components and data. +* **Resilience (or Availability)** is about surviving failures. We achieve it by creating copies ([replicas](https://docs.victoriametrics.com/victoriametrics/cluster-victoriametrics/#replication-and-data-safety)) of our components and data. * **Scalability (or Performance)** is about handling load. We achieve it by [adding more components](https://docs.victoriametrics.com/victoriametrics/#scalability-and-cluster-version) on every layer to distribute the work. The architectures in this guide are simply different combinations of these two approaches, designed to handle a specific blast radius.