Gain insights into using gRPC in ASP.NET Core. Discover remote procedures, Protobuf serialization, advanced features, and performance best practices to create low-latency, high-throughput applications.

gRPC on ASP.NET Core - the complete guide.png

dotnet.tar.gz

.NET gRPC Server

.NET gRPC Client and Server

.NET gRPC Client web app and Server

.NET gRPC setup with SSO

.NET gRPC-Web Client and Server

gRPC is a high-performance communication protocol that works over either HTTP/2 or HTTP/3. It can be used by any programming language and framework, including .NET. gRPC libraries with client and server components are included in ASP.NET Core—the main web development framework of .NET. 

In this course, you’ll walk through all key parts of using gRPC on .NET. Next, you’ll learn how to use all types of remote procedures supported by gRPC. Then, you’ll get familiar with Protobuf, which is the main message serialization protocol used by gRPC. Next, you’ll learn both the fundamentals of Protobuf and its advanced features, including the ability to extend it. After covering the gRPC fundamentals, you’ll go through some of its advanced features, which include API versioning and performance best practices.

By the end of this course, you’ll have learned how to create gRPC applications on ASP.NET Core and create low latency and high throughput applications that are especially useful for time-sensitive applications.

The Ultimate Guide to gRPC in ASP.NET Core

All of the call types above are supported.

Which call type is not supported by gRPC?

Which call type is not supported by gRPC?

By not having the `stream` keyword next to the parameters

By having the `stream` keyword only next to the request parameter

By having the `stream` keyword only next to the response parameter

In Protobuf, how can you define a unary call?

In Protobuf, how can you define a unary call?

A `Task` containing a collection of the response objects

An object of the `ServerCalLContext` type

What is the return type of a C# implementation of a server-streaming call?

What is the return type of a C# implementation of a server-streaming call?

When the rest of the stream is filled and completed

A new instance of the method on the server is triggered for every message put on the stream.

When a client writes a message into the stream, when does the server receive it?

When a client writes a message into the stream, when does the server receive it?

For each message read from the request stream, there can be exactly one message written into the response stream.

All messages need to be read from the request stream before the response stream can be populated.

The request stream needs to remain open as the response stream is populated.

The two streams can be used completely independently from each other.

What is the relationship between the client stream and server stream in a bi-directional gRPC call?

What is the relationship between the client stream and server stream in a bi-directional gRPC call?

Test your knowledge of different call types in gRPC.

Basics of gRPC on .NET

Overview of Protobuf

Extending Protobuf Functionality

gRPC Call Types

Configuring gRPC Applications

Scaling out gRPC Applications

Securing gRPC Applications

Monitoring gRPC Applications

Advanced gRPC Usage

Conclusion

Appendix

Quiz: gRPC Call Types