Book Image

Microservices Communication in .NET Using gRPC

By : Fiodar Sazanavets
Book Image

Microservices Communication in .NET Using gRPC

By: Fiodar Sazanavets

Overview of this book

Explore gRPC's capabilities for faster communication between your microservices using the HTTP/2 protocol in this practical guide that shows you how to implement gRPC on the .NET platform. gRPC is one of the most efficient protocols for communication between microservices that is also relatively easy to implement. However, its official documentation is often fragmented and.NET developers might find it difficult to recognize the best way to map between C# data types and fields in gRPC messages. This book will address these concerns and much more. Starting with the fundamentals of gRPC, you'll discover how to use it inside .NET apps. You’ll explore best practices for performance and focus on scaling a gRPC app. Once you're familiar with the inner workings of the different call types that gRPC supports, you'll advance to learning how to secure your gRPC endpoints by applying authentication and authorization. With detailed explanations, this gRPC .NET book will show you how the Protobuf protocol allows you to send messages efficiently by including only the necessary data. You'll never get confused again while translating between C# data types and the ones available in Protobuf. By the end of the book, you’ll have gained practical gRPC knowledge and be able to use it in .NET apps to enable direct communication between microservices.
Table of Contents (17 chapters)
1
Section 1: Basics of gRPC on .NET
5
Section 2: Best Practices of Using gRPC
9
Section 3: In-Depth Look at gRPC on .NET

Proxy load balancing with gRPC

Proxy load balancing is the most popular type of load balancing used by standard web applications. With it in place, the client doesn't know the exact addresses of individual endpoints. It only knows the address of a single endpoint that the proxy is hosted on. And it's the job of the proxy to then redirect the request to the actual endpoints.

Large-scale user-facing applications would use this type of load balancing. Because web applications like Facebook or YouTube would not be able to support the number of requests they receive if they just ran as a single instance, they have to be scaled out and run as many duplicate instances. The number of these instances may change as the number of requests changes. Also, the instances may get moved to different hardware if the original machine fails, which regularly happens in data centers.

As the user, you would never be expected to know the ever-changing list of the endpoint addresses. All you...