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

Summary

In this chapter, you have learned why API versioning in gRPC is important when using public endpoints or clients that have been developed by external teams. You now know that the sequence numbers of Protobuf fields are used as field identifiers during the transit of the message, while human-readable field names are simply labels. However, despite the fact that changing the field name to any arbitrary value will not break interface compatibility, modifying the existing fields in any way is still not a good practice.

You have learned that the safest way to change a Protobuf definition without causing compatibility issues is to either remove some fields or add new fields with new sequence numbers. Any fields that haven't been populated will be populated with default values by gRPC middleware. Any fields that don't exist in a Protobuf definition will be ignored if they are present in the message.

You are now aware that to prevent anyone from accidentally adding...