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

How to factor in API versioning at the design stage

There are some standard ways of applying versioning to REST APIs. Usually, you will have some subpath in your URL that contains the version number. This way, you can host several different versions of the API simultaneously. And your clients will never communicate with the wrong version, as the version number will be written into the address that they submit requests to.

For example, you may have a URL like this:

https://example.com/status/v1

In this example, v1 would represent the API version number. Then, if you need to update your API, you will not modify the original endpoints. Instead, you will host another version of it at the address that ends with v2. This way, the functionality of the existing clients will not change at all, as nothing in the backend that they are talking to would have changed. And this is why you don't have to worry about your new API being compatible with the old clients.

The same principles...