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

Where SignalR would beat gRPC

SignalR is an ASP.NET Core library that enables real-time two-way communication between the client and the server. It can do everything that gRPC can do (making requests, receiving responses, streaming data to and from the client, and streaming data from the server). But in addition to this, it can also send data from the server to the client without receiving a request first.

Because SignalR runs over HTTP/1.1, it requires a persistent connection and it uses a fairly verbose JSON payload, so perhaps it's not the best tool to be used in the backend of a distributed microservice application. But it's ideal for browsers and it's relatively effortless to set up too, as we will see now.

Setting up a SignalR application

Create an ASP.NET Razor Pages project by executing the following command. This command can be executed from any folder of your choice, as this will be a standalone application:

dotnet new webapp -o SignalrApplication...