What problem does it solve?
Resilience patterns prevent your .NET 10 application from failing immediately when external dependencies (HTTP APIs, databases, queues) experience transient outages, latency spikes, or throttling.
Core Features & Use Cases
- Polly v8 resilience pipelines: Build composable
ResiliencePipeline handlers (retry, circuit breaker, timeout, fallback, rate limiting, hedging) instead of legacy Polly v7 policies.
- HTTP client resilience via DI: Use
AddResilienceHandler/AddStandardResilienceHandler with HttpClientFactory so resilience is applied consistently at the client layer.
- Non-HTTP operation pipelines: Register named pipelines with
AddResiliencePipeline for database, queue, and other operations, including timeout and retry logic.
- Telemetry-ready monitoring: Instrument retries, circuit breaker state, and timeouts for operational visibility using Polly v8 metrics/OpenTelemetry patterns.
- Safety guardrails: Avoid anti-patterns like retrying non-idempotent writes and ensure timeouts are always configured.
Quick Start
Add a standard resilience handler to your HttpClient so retry, circuit breaking, and timeouts are automatically applied to outbound calls.