dotnet-resilience

You add fault tolerance to ASP.NET Core apps by configuring resilience pipelines with Polly v8 and Microsoft.Extensions.Http.Resilience. This integrates retry, circuit breaker, and timeout strategies via dependency injection to protect against transient failures and service unavailability.

A resilience pipeline in .NET is a sequence of fault tolerance policies like rate limiting, timeouts, and retries applied to HTTP requests. You need it to prevent application failures caused by transient network issues or downstream service unavailability.

Yes, you can configure custom resilience pipelines for specific HTTP clients. This allows fine-grained control over retry and circuit breaker policies tailored to distinct scenarios like external API calls or database interactions.

Yes, Microsoft.Extensions.Http.Resilience works directly with dependency injection. It enables you to add standard resilience handlers to named HTTP clients, such as 'catalog-api', using sensible defaults configured within the ASP.NET Core service collection.

The best way to prevent cascading failures in .NET microservices is implementing a circuit breaker pattern. By using Polly v8, the circuit breaker stops sending requests to an unavailable downstream service, automatically retrying failed requests once the service recovers.

Your .NET application might still fail if standard retry policies lack a circuit breaker or timeout. Combining retries with circuit breakers and rate limiting via a custom Polly v8 pipeline prevents cascading failures during sustained downstream service unavailability.