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

Questions

  1. What would happen if you changed the name of one of your fields in the Protobuf message definition on your client but not on the server?
    1. It will make the interface incompatible with the server.
    2. It will throw an error unless you also change the sequence number.
    3. It will not affect the functionality.
    4. The server will associate the value with the wrong field.
  2. Which of these data types cannot be interchanged?
    1. Bytes and string
    2. sfixed32 and int32
    3. uint64 and int32
    4. uint64 and bool
  3. What would happen if you removed a field from a Protobuf response message definition on the server, but not on the client?
    1. It will be populated with the default value on the client.
    2. It will make the client incompatible with the server.
    3. The client will have mismatching field values.
    4. No error will be thrown, but the client will not be able to interpret the data.
  4. What's the best way to prevent new fields from being accidentally reinstated with the sequence numbers of the old fields that have been removed...