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 that it's possible to use nullable data types in Protobuf messages. Even though nullable data types aren't natively available in Protobuf, they can be added to it by importing wrapper data types from Google's library of well-known types.

You have also learned that although there is no native support for time and duration data in Protobuf, there are Timestamp and Duration data types that have been designed specifically for this purpose. These data types need to be imported into your Protobuf definitions individually.

You now also know that although it is possible to create a Protobuf message definition with no fields, the library of well-known types already has a standardized message definition specifically to be used as an empty object. Unsurprisingly, it is called Empty.

We have also covered two ways you can use loosely typed fields in Protobuf. There is the Any data type, which you can use to assign any arbitrary message...