liveBook · Manning

gRPC

As explained in ASP.NET Core in Action, 3e

gRPC is a high-performance, language-independent remote procedure call framework for service-to-service communication.

gRPC is a modern, language-independent remote procedure call framework for building efficient binary APIs between servers. In ASP.NET Core, it provides a focused alternative to ordinary HTTP APIs when service-to-service communication is the priority. section 1.2 section 2.4.3

Choose gRPC when:

  • A backend service needs to call another backend service through an efficient binary API. section 1.2
  • A contract-based RPC programming model fits better than a conventional REST or HTTP API. section 2.4.3
  • You want to combine multiple ASP.NET Core paradigms in one application and dedicate gRPC to service-to-service calls. section 1.2

Selecting an API style

An ASP.NET Core application can serve HTML pages to traditional clients, expose a REST API to a browser-based single-page application, and provide an ad hoc RPC service to another client. gRPC is the suitable choice in that last service-to-service role when efficient binary communication is needed. section 1.2

How ASP.NET Core in Action, 3e covers it

How deep it goes
Defines gRPC and contrasts it with HTTP APIs and WCF, but does not explain contracts, transport, or implementation steps.
Examples
Shows server-to-server binary APIs and an ad hoc RPC service alongside HTML and REST API clients.
What you can do after
Evaluate whether gRPC fits an efficient server-to-server API or a contract-based RPC migration from WCF.
How it connects
Connects gRPC with ASP.NET Core, RPC, HTTP APIs, REST APIs, and Windows Communication Foundation.

Also explained in

Compare how 10 books explain gRPC →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.