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. For the best performance in terms of gRPC communication, which of the following client-side objects would you need to reuse?
    1. Client
    2. Channel
    3. Both the client and the channel
    4. Neither
  2. What is the default concurrent stream limit on the HTTP/2 connection?
    1. 1,000
    2. 10
    3. 100
    4. 1
  3. What happens if no data is received within the timeout window after sending a keep-alive ping?
    1. The connection is terminated
    2. The next ping is sent
    3. The connection is marked as idle
    4. This configuration parameter is made redundant
  4. How do you define a bi-directional streaming call in Protobuf?
    1. Apply the stream keyword before the rpc keyword
    2. Apply the stream keyword after the rpc keyword
    3. Apply the stream keyword before the input parameter
    4. Apply the stream keyword before both the input and output parameters
  5. When shouldn't you use UnsafeByteOperations.UnsafeWrap to populate ByteString?
    1. When you intend to modify the original byte array after this call
    2. You should be able to use it in any situation
    3. When you haven&apos...