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

Chapter 6: Scaling a gRPC Application

If you expect your web application to support a high number of connections, running a single instance of it will not be enough. You will have to scale it.

There are two types of scaling you can do – scaling up and scaling out. Scaling up is when you add more hardware to the machine running the server-side components of your application. This is a pure hardware solution and it has its limits. Therefore, we will not cover it in this chapter.

Scaling out, on the other hand, is when you run multiple instances of the same application, so any particular instance of it will not be overwhelmed by an excessive number of connections. The connections will be distributed evenly between the running instances.

The ability to easily scale out granular components of a distributed application is one of the main purposes of microservices architecture. This is what we will cover in this chapter.

To evenly distribute incoming connections between...