Resilience Demo: naive vs. resilient integration

What the resilient client does differently

The naive client is a plain HttpClient call — no retry, no timeout override, no circuit breaker. The resilient client wraps the same call in a Polly v8 pipeline via Microsoft.Extensions.Http.Resilience:

• Retry with backoff + jitter — Transient failures (a dropped connection, a momentary 500) get a few automatic retries with exponential backoff, instead of surfacing to the caller on the first hiccup.
• Circuit breaker — Once failures cross a threshold, the breaker opens and fails fast for a cooldown window — no point hammering a dependency that's already down. It half-opens automatically to test recovery, then fully closes once healthy again.
• Per-attempt timeout — Each individual attempt is bounded, not the whole retry budget — a hung call doesn't block the pipeline from moving on to the next attempt or, once the breaker opens, failing fast.
• Graceful fallback — When the pipeline ultimately can't get a real answer, the endpoint returns a clear "temporarily unavailable" response instead of an unhandled 500 — the caller gets something predictable to handle.