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 5: Applying Versioning to the gRPC API

So far, we have had a look at the uses of gRPC in ASP.NET Core where both the client and server applications are present in the same solution and rely on the same reference library. When this is the case and the applications at both ends of gRPC communication are in the same repository, then those components are probably meant to be deployed together. This is where API versioning is not critical, as you can simply apply Protobuf changes to both the client and server at the same time. Even if these are breaking changes, only the applications from the same repository will be affected.

But not all gRPC implementations are like this. Quite often, your client and your server will be in different repositories and will be deployed as separate components. It might even be the case that the client and the server are developed by separate teams or even separate organizations. Just like with a REST API, your server might have a public gRPC endpoint...