Why should you care?

ShopNest should standardize resilience instead of hand-rolled loops in every client.

See it live — copy this example

Paste into a C# console or class library project and run dotnet run.

// Pseudo-config matching Polly usage
// policy = WaitAndRetryAsync(3, i => TimeSpan.FromMilliseconds(200 * i))
// httpClient.AddPolicyHandler(policy)
Console.WriteLine("Polly: retry 3x with backoff on HttpRequestException");
Console.WriteLine("Polly: wrap timeout 3s around PSP call");

What happened?

• Prefer Polly (or Microsoft.Extensions.Http.Resilience) over custom retry helpers for production.
• Combine timeout + retry carefully to avoid multiplying load.

Practice next

1. Add Polly to an HttpClient in ShopNest.
2. Retry only transient HTTP statuses.
3. Add a total timeout policy.
4. Add jitter to waits.
5. Different policy for inventory vs payment.

Remember

Declarative policies. HttpClient integration. Compose timeout + retry wisely.

ShopNest typed HttpClient + Polly

PaymentClient uses retry+timeout policies.

Outcome: Consistent resilience without copy-paste loops.