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 the fundamental principles of authentication and authorization and how to apply both to gRPC endpoints. You now know that authentication is when the user proves that they are who they claim to be, while authorization is making sure that the user has the necessary permissions to access a resource.

You have learned how a separate application can act as an SSO provider to allow you to authenticate a user into all applications inside your ecosystem. You have learned how the OpenID Connect protocol is used to authenticate the user into a relevant application, while OAuth is used for user authorization.

You have learned that a JWT contains a JSON payload object that describes the user so that the protected application can tell whether the user is who they claim to be and whether they have the necessary permissions. A JWT is validated by a signature to protect it from forgery.

And this concludes the chapter on applying authentication and...