resilience

Configure HttpClient resilience in .NET 10 by registering IHttpClientFactory and using AddStandardResilienceHandler or AddResilienceHandler to apply retry, circuit breaker, and timeout policies per external service. Polly v8 ResiliencePipeline composition chains these strategies without manual nesting to prevent cascading failures.

Handle transient failures in .NET by building composable Polly v8 ResiliencePipeline instances that manage retries, circuit breaking, timeouts, fallback, hedging, and rate limiting. These DI-friendly pipelines keep call sites simple while handling fragile network interactions and database or message queue operations.

Yes, Polly v8 hedging supports latency-sensitive reads in .NET applications. Resilience pipelines can be composed and tuned per service to execute hedged requests, falling back to alternate calls when primary external API interactions exceed acceptable latency thresholds.

Polly v8 ResiliencePipeline telemetry integrates with OpenTelemetry by emitting metrics compatible with its monitoring standards. This provides production-safe defaults and observability for timeout tracking, circuit breaker state changes, retry attempts, and overall resilience pipeline health.

Yes, Polly v8 supports typed pipelines via AddResiliencePipeline for non-HTTP scenarios including database and message queue operations. You can inject keyed pipelines for testability, applying resilience strategies to typed return scenarios beyond standard HttpClient factory integrations.

Use AddStandardResilienceHandler to apply default retry, circuit breaker, and timeout policies for an external API, while AddResilienceHandler allows custom named handlers for per-service resilience tuning. Both integrate with IHttpClientFactory to manage network interactions in .NET 10.