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

What the sequence numbers in the proto file represent

What makes Protobuf different from any other communication protocols or data storage formats is that each field, in its objects, has an equality sign (==) at the end, followed by a unique integer number. The equality sign followed by a numeric value is how you would normally assign a numeric value to a variable, but in Protobuf, it represents a unique sequence number of the field.

The reason these sequence numbers exist is that they are the only field identifiers that are used when the message is being transferred between the client and the server. The Protobuf messaging format has been designed to be as efficient as possible. Using arbitrary byte arrays to represent human-readable field names isn't very efficient. Instead, using numeric identifiers is the simplest way of both keeping track of each unique field and keeping the data payload size as small as possible.

Another feature that makes Protobuf so efficient is...