dotnet-resiliency-ai-kit

To add a retry policy and circuit breaker to .NET HttpClient, configure Microsoft.Extensions.Http.Resilience using AddStandardResilienceHandler. This applies an ordered resilience pipeline to prevent cascading failures from transient HTTP errors.

Yes, you can apply standard resilience handlers to Refit clients in .NET. Configuring AddStandardResilienceHandler on your Refit client protects upstream calls from transient faults, timeouts, and overload scenarios using rate limiting and circuit breaking.

Handle HTTP 503 and 429 responses in .NET by applying a standard resilience pipeline. This configuration enables selective retries with exponential backoff and rate limiting to reduce impact from transient dependency errors and prevent cascading failures.

The default resilience pipeline order in Microsoft.Extensions.Http.Resilience applies rate limiting, total request timeout, retry with exponential backoff, circuit breaker, and per-attempt timeout to ensure reliable outbound HTTP communication.

Use a custom resilience handler instead of AddStandardResilienceHandler when the default retry and circuit breaker behavior is not appropriate for your scenario. You can configure a named custom pipeline using AddResilienceHandler for granular control.

Yes, .NET HttpClient supports rate limiting for outbound HTTP calls. By configuring Microsoft.Extensions.Http.Resilience, you can apply rate limiting as part of the standard resilience pipeline to protect upstream services from overload scenarios.