Chapter 10 – gRPC Fundamentals

1. RPC stands for Remote Procedure Call. A client can call an exposed procedure on a remote server, which is just like calling a local procedure but it gets executed on a remote server. An RPC is best suited for inter-service communication in connected systems.
2. gRPC is based on client-server architecture, whereas this is not true for REST. gRPC also supports full-duplex streaming communication in contrast to REST. gRPC performs better than REST as it uses the static paths and single source of the request payload.
3. A REST response error depends on HTTP status codes, whereas gRPC has formalized the set of errors to make it well-aligned with APIs. gRPC has also been built for supporting and handling call cancellations, load balancing, and failovers. For more information, please refer to the subsection REST versus gRPC.
4. You should use the Server Stream RPC methods because you would like to receive the latest messages from the server,...