From 47bd8726c81c92a6be1bff4743e4076d2a770626 Mon Sep 17 00:00:00 2001 From: greenie-msft <56556602+greenie-msft@users.noreply.github.com> Date: Wed, 2 Nov 2022 15:10:32 -0700 Subject: [PATCH] Update daprdocs/content/en/concepts/resiliency-concept.md Signed-off-by: greenie-msft <56556602+greenie-msft@users.noreply.github.com> --- daprdocs/content/en/concepts/resiliency-concept.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/concepts/resiliency-concept.md b/daprdocs/content/en/concepts/resiliency-concept.md index e2178559d..284176de3 100644 --- a/daprdocs/content/en/concepts/resiliency-concept.md +++ b/daprdocs/content/en/concepts/resiliency-concept.md @@ -3,7 +3,7 @@ type: docs title: "Resiliency" linkTitle: "Resiliency" weight: 400 -description: "Configure retries, timeouts, circuit breakers and monitor app health" +description: "Configure policies and monitor app and sidecar health" --- Distributed applications are commonly comprised of many microservices, with dozens - sometimes hundreds - of instances scaling across underlying infrastructure. As these distributed solutions grow in size and complexity, the potential for system failures inevitably increases. Service instances can fail or become unresponsive due to any number of issues, including hardware failures, unexpected throughput, or application lifecycle events, such as scaling out and application restarts. Designing and implementing a self-healing solution with the ability to detect, mitigate, and respond to failure is critical.