There's not much of a Remote Procedure Call built into the protocol. It's like GraphQL with resolvers. They have you imagine it's a procedure, but you can ign

There's not much of a Remote Procedure Call built into the protocol. It's like GraphQL with resolvers. They have you imagine it's a procedure, but you can ignore that. You can have multiple responses, but they don't keep the analogy going for that. They don't suggest generators. https://grpc.io/docs/what-is-grpc/core-concepts/ https://grpc.io/docs/what-is-grpc/core-concepts/ Here's the golang gRPC Hello World where the interface clearly comes first rather than the procedure. HelloRequest / HelloReply is analogous to HTTP (except with HTTP it's officially a response and you usually see Response in the API but not always [1]). https://github.com/grpc/grpc-go/blob/master/examples/helloworld/greeter_server/main.go#L42 https://github.com/grpc/grpc-go/blob/master/examples/hellowo... To me, this is a good thing. Good protocol, annoying name. 1: https://fastify.dev/docs/latest/Reference/Reply/ https://fastify.dev/docs/latest/Reference/Reply/