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

Chapter 10: Applying Authentication and Authorization to gRPC Endpoints

Authentication and authorization are very important topics in any type of application development. Almost any public-facing application will have at least some of its functionality restricted to only specific users, as you wouldn't want an anonymous user to gain access to sensitive information.

There are many different types of sensitive information that you would want to restrict access to. Personal information of registered users is one example; so is the history of their personal communication with other users; so is any financial information.

There are many examples of this on the public web. No social media platform would allow you to publish content or contact other users until you have logged in with a username and password. Neither would an online banking app grant you access to the account information without verifying who you are.

Because Google Remote Procedure Call (gRPC) endpoints are...