Remote procedure calls and gRPC

Remote procedure calls (RPC) is a distributed computing communication approach, where a program running on one computer calls a a function on another computer as if it were a local function. In essence, RPC follows the request-response pattern, where one computer acts as a client invoking the function, while the other computer acts as a server, executing the function and returning the function call results. When contrasting REST and RPC, REST is resource-based and uses standard HTTP methods, while RPC is function-based and may use custom protocols. There are, however, benefits to using function-based protocols, including the possibility of strongly typed APIs.

Here is where gRPC comes in. gRPC (gRPC Remote Procedure Calls) is a RPC framework that builds on top of HTTP/2 and uses Protocol Buffers for creating strongly typed APIs. As gRPC is built on top of HTTP/2, it is possible to use it in browsers, even though it is not still widely adapted. It is, however, meaningful to know of it's existence, as it's use will increase in the future.

Here, your task is to read the Cloudflare Blog item Moving k8s communication to gRPC and to come up with two good questions on it. The blog entry is available at https://blog.cloudflare.com/moving-k8s-communication-to-grpc/.

For writing the question, refer also to the notes on good questions.

Create your two questions using the widget shown below.

Once you have created the questions, answer to at least five peer-authored questions. After each question, you are given a possibility to rate the question -- please, rate each question that you answer.