What problem does it solve?
Many .NET applications fail unpredictably when downstream services are slow, rate-limited, or intermittently unavailable; this Skill provides patterns and guidance to make calls resilient and observable so services degrade gracefully instead of failing catastrophically.
Core Features & Use Cases
- Standard HTTP Resilience: Apply a sensible default pipeline to HTTP clients to get retry, circuit breaker, and timeout behavior out of the box.
- Custom and Named Pipelines: Create per-backend pipelines with custom retry strategies, jitter, circuit breaker thresholds, timeouts, fallback logic, hedging, and typed results.
- Non-HTTP Support: Apply retry and timeout pipelines to database calls, message handling, or other I/O operations via ResiliencePipeline and DI.
- Use Case: Protect an Orders API client with an exponential-backoff retry plus circuit breaker and a per-attempt timeout, and provide a fallback for degraded responses while emitting telemetry for monitoring.
Quick Start
Add a named HTTP client, apply AddStandardResilienceHandler for defaults, and customize a pipeline with AddResilienceHandler to configure retry, circuit breaker, timeout, and optional fallback strategies.
