The problem with gRPC is the "R". It's been the same with JMI, Corba, ONC-RPC and all the others. Making "procedure calls" remote and hiding them underneath cl

The problem with gRPC is the "R". It's been the same with JMI, Corba, ONC-RPC and all the others. Making "procedure calls" remote and hiding them underneath client libraries means that programmers do not consider the inherent problems of a networked environment. Problems like service discovery, authentication, etc are hidden beneath something that "looks like" a local procedure call. That's one problem, the other is that procedure calls are focusing on the verbs, not the nouns (called "entities" or "resources" in the article). If you can't express an FSM about a noun and what causes its state to change, then how the hell do you know what it does or how changes to its environment affect it? If you don't know whether some procedure call is idempotent, how the hell can you write code that handles the various network failure modes that you have to deal with?