gRPC for ASP.NET Core, a new framework for high performance APIs
summary
gRPC for ASP.NET Core ships available now at .NET Core 3.0 and provides a Kestrel-hosted server plus a fully managed .NET client that uses HttpClient; protobuf-driven codegen generates service bases and strongly typed clients from .proto files (protos-driven codegen). Benchmarks claim protobuf messages are about 25–33% the size of equivalent JSON. Demos show unary and server/bi-directional streaming working end-to-end, but browsers need gRPC-Web proxies, there’s no built-in reconnect, and Azure App Service/proxy support is still limited.
AI-written summary · about
chapters (38)
- 0:00Introduction
- 0:38What is gRPC
- 2:46protobuf
- 3:50binary format
- 4:46Conceptual differences
- 7:14Demo
- 8:28greet proto
- 10:11generated code
- 11:05startup file
- 12:41service references
- 14:30calling the service
- 16:33launching the service
- 19:13routes
- 23:29Why use gRPC
- 24:31gRPC vs protobuf
- 25:13Headofline blocking
- 26:06HGP vs OH
- 26:37Cogeneration
- 27:10References
- 27:58Server
- 28:30Client
- 29:25Supported languages
- 30:31Streaming
- 32:30GRPC on the wire
- 34:46GRPC response
- 37:27Service streaming
- 44:05Why isnt gRPC everywhere
- 49:20Resources
- 51:05GRPC with load balancers
- 51:55Google protobuf
- 53:08Versioning
- 55:16Reconnecting
- 55:55Async
- 56:35HTTP Poly
- 57:08Publish Contracts
- 57:39Sharing Options
- 58:25Authentication
- 59:19Azure Functions
related talks
01h 00mBuilding ASP.NET Core Kestrel
50mgRPC Web: It’s All About Communication
22mGRPC: Lightning fast self documenting APIs
28mFrom Backend Powerhouses to Web-Friendly APIs: Unlocking
17mBoost API Performance: gRPC vs REST vs Async
26mAdopting gRPC for Low Latency, High Bandwidth Scenarios
01h 01mBuilding Microservice Communication with gRPC
24mHow We Built Protosockets to Go Beyond HTTP and gRPC