Why should you care?

ShopNest slow search must not exhaust threads needed for checkout.

See it live — copy this example

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

// Separate pools (conceptual)
Console.WriteLine("checkout HttpClient pool: 50 connections");
Console.WriteLine("search HttpClient pool: 10 connections");
Console.WriteLine("search saturation != checkout starvation");

What happened?

• Limit concurrency per dependency.
• When search is saturated, checkout still has its own capacity.
• Polly bulkhead and separate typed clients help.

Practice next

1. Create separate HttpClients for ShopNest deps.
2. Cap search concurrency lower than checkout.
3. Measure queue waits per bulkhead.
4. Reject with 503 when bulkhead full.
5. Dashboard per-pool usage.

Remember

Isolate capacity. Protect critical paths. Cap noisy neighbors.

ShopNest pool isolation

Search storms fill only the search bulkhead.

Outcome: Checkout keeps responding.