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

Introduction to load balancing

When you have multiple instances of the same service running in the backend of your server, you will need to implement some kind of a gateway that will decide which particular instance any particular client would connect to. This gateway software would need to have a logic that will decide which specific instance any specific client connection will need to go to. This is what load balancing is.

A load balancer is a piece of software that is positioned between the client and the server-side application instances. It can be a component of the client application itself, or it can be a proxy that the client communicates directly with.

But regardless of what type of load balancer you use, its operation principles will be the same. When it receives the instruction from the client to send a request to the server, it will decide which specific server-side endpoints the request should go to.

We will now build a basic distributed application to demonstrate...