REST vs RPC

API design: Understanding gRPC, OpenAPI and REST and when to use them: the Remote Procedure Call (RPC) model, in which the addressable entities are procedures, and the data is hidden behind the procedures. In [REST], the addressable entities are “data entities” (called “resources” in the HTTP specifications), and the behaviors are hidden behind the data—the behavior of the system results from creating, modifying, and deleting resources. also: A signature characteristic of [REST] is that clients do not construct URLs from other information—they just use the URLs that are passed out by the server as-is.