Start Debugging

Tag: grpc

3 posts

2026-10-31 grpc aspnetcore dotnet

grpc-dotnet 2.85 Enforces MaxReceiveMessageSize After Decompression, Not Just Before

Grpc.AspNetCore and Grpc.Net.Client 2.85.0 now apply MaxReceiveMessageSize to the decompressed size of gzip and deflate messages. A 260 KB request that inflates to 256 MiB is rejected with ResourceExhausted, but legitimate large compressed payloads can start failing too.

2026-08-06 comparison dotnet dotnet-11

gRPC vs REST vs SignalR for service-to-service calls in .NET 11

For internal service-to-service calls in .NET 11, default to gRPC when you own both ends of the contract and the call is point-to-point. Use REST with JSON when anything you do not control has to call the service. SignalR is not an RPC transport between services: reach for it only when one producer has to fan a message out to many long-lived consumers.

2026-01-10 grpc dotnet dotnet-10

gRPC in Containers Feels “Hard” in .NET 9 and .NET 10: 4 Traps You Can Fix

Four common traps when hosting gRPC in containers with .NET 9 and .NET 10: HTTP/2 protocol mismatches, TLS termination confusion, broken health checks, and proxy misconfiguration -- with fixes for each.