> In that sense, REST in practice has always been just RPC without a clear spec for procedure call like XML or JSON RPC. HTTP, even when used without hypermedi

> In that sense, REST in practice has always been just RPC without a clear spec for procedure call like XML or JSON RPC. HTTP, even when used without hypermedia, still has interesting features that are not found in traditional RPC. For example, you can’t just stick nginx in front of your gRPC server and tell it to cache stuff. You can’t tell your Thrift client to retry all idempotent requests automatically (without enumerating the functions that are idempotent). Not to mention upcoming things like HTTP/2 push and 103 (Early Hints). I like to think that HTTP is less of a leaky abstraction over the network.