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 learned that gRPC supports four types of calls – unary, client streaming, server streaming, and bi-directional streaming. You learned that in a Protobuf definition, the type of the call is controlled by the stream keyword or a lack thereof.

We looked at the server-side method signatures that are used for implementing gRPC calls of different kinds. Each of these signatures includes the context parameter, as well as the actual request and response data. This parameter is used for extracting metadata from the call, which may include user information and request headers.

You also learned that a gRPC channel can be configured by using the GrpcChannelOptions object. This object allows you to restrict the message's size, reuse HttpClient, apply any custom middleware logic, and more.

We also looked at what happens when multiple gRPC implementations correspond to the same HTTP path. If those paths have identical service and rpc names, an error...