Re:Application Load Balancers enables gRPC workloads with en...
by halter73 on Friday October 30, 2020 @10:28PM
(#24948677)
The default ASP.NET Core server is Kestrel which runs in-process and is cross platform. Kestrel has officially supported gRPC for over a year now[1]. That linked GitHub comment is specifically about IIS gRPC support which relies on HTTP.sys (which runs in kernel mode and is tied to the Windows shipping cycle as noted).
[1]: https://docs.microsoft.com/en-us/aspnet/core/grpc/?view=aspn...
Re:Application Load Balancers enables gRPC workloads with en...
by ComputerGuru on Friday October 30, 2020 @03:32PM
(#24945988)
> Really illustrates the dumbassery of sticking a (relatively) fast-moving application-layer protocol into the kernel.
Really? There are lots of problems with doing HTTP in the kernel, but “fast moving” is a new one. HTTP was stuck in permafrost from 1995 to 2015. If it weren’t for Google, neither of HTTP 2 or 3 would have ever happened.
Might have been handy to beat benchmarks back in the day when people liked to whip them out for comparison, but IIS is under 10% according to Netcraft now. Time to fold up the tent and go home.
I suppose .Net Core is sticking with Http.sys to avoid implementing their own web server, but is tying yourself to the Windows shipping cycle worth it ?