Overview

Mon, 01 Jan 0001 00:00:00 +0000

Dapr provides the capability for defining and applying fault tolerance resiliency policies via a resiliency spec. Resiliency specs are saved in the same location as components specs and are applied when the Dapr sidecar starts. The sidecar determines how to apply resiliency policies to your Dapr API calls.

In self-hosted mode: The resiliency spec must be named resiliency.yaml.
In Kubernetes: Dapr finds the named resiliency specs used by your application.

Policies

You can configure Dapr resiliency policies with the following parts:

Targets

Mon, 01 Jan 0001 00:00:00 +0000

Targets

Named policies are applied to targets. Dapr supports three target types that apply all Dapr building block APIs:

apps
components
actors

Apps

With the apps target, you can apply retry, timeout, and circuitBreaker policies to service invocation calls between Dapr apps. Under targets/apps, policies are applied to each target service’s app-id. The policies are invoked when a failure occurs in communication between sidecars, as shown in the diagram below.

Error recovery using resiliency policies on Dapr Docs

Overview

Policies

Targets

Targets

Apps