rms/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2026-05-17 00:26:36 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs/guides: use canonical link

Browse Source
This commit is contained in:
Max Kotliar
2025-11-05 21:09:19 +02:00
parent c90c7c3123
commit d5705a9647
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/guides/vm-architectures/README.md
View File

@@ -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.