Hands-On Software Engineering with Golang

Comparing gRPC to REST

While using REST as an architecture for building APIs provides several benefits, it also comes with a few caveats attached. Let's examine these caveats in more detail.

REST APIs are typically implemented on top of the HTTP/1.x protocol, which lacks proper support for managing and reusing connections. As a result, clients must establish a new TCP connection with the backend server and perform a complete TLS handshake every time they wish to invoke an API endpoint. This requirement not only incurs additional latency to API calls but also increases the load on backend servers (or load balancers, if you are doing TLS termination at the edge) since TLS handshaking comes with a non-insignificant computation cost.

In an attempt ...