gRPC Contract Design

In a REST API, a caller can read the documentation and try an operation with an ordinary HTTP client. In gRPC the contract starts somewhere else: one schema file, from which both the client and the server generate code.

That changes the notation. It does not change the design responsibility. You still have to define who calls, which operations exist, what every field means, which failures are stable, whether a call may be retried, how long it may take, and how the contract changes without breaking callers already running.

The most permanent decision here is not the method name