gRPC is an emerging standard for cross-platform remote procedure calls (RPCs) over HTTP that was originally created by
Google (the g in gRPC) and offers efficiency and scalability benefits. gRPC may be the future standard for web services, but it cannot
be used in web applications because it requires low-level control of the HTTP messages that it sends, which browsers do not allow.
(There is a browser library that allows gRPC to be used via a proxy server, but that undermines the benefits of using gRPC.) Until
gRPC can be used in the browser, its inclusion in
ASP.NET Core is of interest only for projects that use it for communication between
back-end servers, for which many alternative protocols exist. I may cover gRPC in future editions of this book but not until it can be
used in the browser or becomes the dominant data-center protocol.