2 ms·
After three decades of minimal-to-mixed success, you would really think people would have figured out by now that RPC is a fundamentally flawed metaphor. It's
by ajross 19y ago
After three decades of minimal-to-mixed success, you would really think people would have figured out by now that RPC is a fundamentally flawed metaphor. It's not pipelineable, which means that it's always going to be slow. It's a deadlock waiting to happen. And it's obscure: it takes the simple notion of calling a method (say, to extract a single field) and hides from the programmer the fact that this simple object might live on another side of a content. Just a disaster.
Without exception, every successful network protocol has a query/response structure. Even things that are "technically" based on an "RPC" protocol (NFS) have evolved in this direction for performance and simplicity. Take a look at the code for an NFS stack and see if you can see the "procedure calls" to the remote server. They aren't there.