- Course
Resilient Communications in C# 14
Downstream services fail. A slow or failing API should never take your service down with it. Learn to build HTTP and gRPC clients in C# 14 that stay reliable through timeouts, outages, and throttling.
- Course
Resilient Communications in C# 14
Downstream services fail. A slow or failing API should never take your service down with it. Learn to build HTTP and gRPC clients in C# 14 that stay reliable through timeouts, outages, and throttling.
Get started today
Access this course and other top-rated tech content with one of our business plans.
Try this course for free
Access this course and other top-rated tech content with one of our individual plans.
This course is included in the libraries shown below:
- Core Tech
What you'll learn
In a distributed system, the calls between services are where things quietly break. A downstream API times out, a dependency starts throttling you, half of a batch of requests fails while the rest succeed, and suddenly a small hiccup upstream turns into an outage in your own service. Writing code that makes a call is easy. Writing code that keeps working when that call goes wrong is the real job. In this course, Resilient Communications in C# 14, you'll gain the ability to consume HTTP and gRPC services that hold up under real production conditions. First, you'll replace fragile HttpClient usage with IHttpClientFactory and learn to attach and refresh auth tokens without touching your call sites. Next, you'll build resilience pipelines with Polly, adding retries, timeouts, circuit breakers, and hedging where each one actually helps. Then you'll take on gRPC, modeling contracts with Protobuf and applying the same resilience to high-performance calls. Finally, you'll handle the hard cases: long-lived streams that drop, concurrent fan-outs that partially fail, client-side rate limiting so your retries do not make things worse, and distributed tracing that lets you follow one request across every service. When you're finished, you'll have the skills and knowledge of resilient service communication in C# 14 needed to build clients that survive a bad day upstream, whether they talk over HTTP or gRPC.