4 ms·
Ok, the people being quoted on the page all look to be under 25, and so are the people commenting here judging by the comments, so I suspect that no one involve
by mcguire 14y ago
Ok, the people being quoted on the page all look to be under 25, and so are the people commenting here judging by the comments, so I suspect that no one involved or interested in Bridge has ever used RPC systems before and therefore have no idea how bad they actually are. Or possibly, judging by the "No configuration files or IDLs." comment, they may have heard of SOAP while it was being called an RPC system and be suffering from second system delusions.
If you are interested in some of the existing discussion, check out (They're PDFs. Sorry.):
* [1988] A Critique of the Remote Procedure Call Paradigm http://www.cs.vu.nl/~ast/publications/euteco-1988.pdf http://www.cs.vu.nl/~ast/publications/euteco-1988.pdf
* [1994] A note on distributed computing. http://research.sun.com/techrep/1994/abstract-29.html http://research.sun.com/techrep/1994/abstract-29.html
* [2005] RPC under fire. Steve Vinoski. http://www.iona.com/hyplan/vinoski/pdfs/IEEE-RPC_Under_Fire.pdf http://www.iona.com/hyplan/vinoski/pdfs/IEEE-RPC_Under_Fire....
- dshankar 14y agoSo Google (Protocol Buffers - RPC), Facebook (Thrift - RPC), Twitter (Finagle/Thrift - RPC), GitHub (BERT-RPC), DotCloud (ZeroRPC), Quora (Thrift - RPC) and all major tech companies are wrong? The list of companies using RPC messaging systems is very long. RPC is widely used. It is mature and well understood. "RPC is bad because network calls look like local calls" is a terrible overused argument.
- m0th87 14y agoTo some degree, it's a fair critique. RPC is a loaded term, because there were far too many implementations that tried to hide the network, which is a recipe for disaster. We were hesitant of going forward with the name ZeroRPC ourselves because of the historical baggage. That said, most of the faults people have placed on RPC have been products of individual implementations and not the concept itself, and there really is much more momentum behind RPC engines than anything else. For my Master's thesis, I implemented a generative communication [1] engine. While I still feel like it's a "beautiful" model, it turns out no one cares. Developers understand RPC calls. Not that many get tuples / tuplespaces / pattern matching and why that can be nice. 1: http://theory.sci.univr.it/papers/Isa-orig/Varie/Linda2.pdf http://theory.sci.univr.it/papers/Isa-orig/Varie/Linda2.pdf
- chubot 14y agoThe terms are fuzzy, but tuple spaces aren't solving the same problem RPC. That is, you can _use_ RPC to implement tuple spaces. But not the other way around! Message queues are basically the modern tuple spaces, and I'll bet all the companies listed above use message queues too. RPC has its place but it's overused. It's a low level primitive, not a distributed systems architecture. Some people's architecture is basically just RPC spaghetti, with a naive handling of errors. The argument is confused by the fact that you can use an RPC with messaging semantics (async, a single argument data payload), and you can use a messaging system with RPC semantics (i.e. tunneling RPC over HTTP, using HTTP as transport). I think we basically have to stop using the word RPC as a catch-all for so many systems, and identify which choices are good and which ones lead to design mistakes.
- m0th87 14y agoYou can implement RPC in tuplespaces pretty easily: Client: out("rpc-request", uuid, "say_hello", "m0th") in("rpc-request", uuid, ?response) Server: in("rpc-request", ?uuid, ?method, ?arg) response = call(method, arg) out("rpc-request", uuid, response) The example is obviously a bit simplified, but it's certainly easy to do in generative communication. Message queues and tuplespaces are very different. A tuplespace allows pattern matching on tuples. And many tuplespace implementations do not provide monotonicity.
- chubot 14y agoWell I should have clarified that I was basing that on my interpretation of the terms RPC and message queue. The important bit is that all these debates are obscured by imprecise terminology. RabbitMQ supports reciving messages based on a pattern: http://www.rabbitmq.com/tutorials/tutorial-five-python.html http://www.rabbitmq.com/tutorials/tutorial-five-python.html It also says it supports RPC: http://www.rabbitmq.com/tutorials/tutorial-six-python.html http://www.rabbitmq.com/tutorials/tutorial-six-python.html That doesn't match my definition of RPC, but OK. I consider RPC server-to-server, not server -> "smart" intermediary -> server. But I guess they want to to define RPC as request/reply. So again it's a terminology issue. What deployed, modern systems use tuple spaces and are substantively different from a message queue? My impression is that "tuple spaces" were the historical name, from Gelertner's papers, but everyone just calls them message queues. Message queues have lots of different properties but the defining one, as in tuple spaces, is that there's an intermediary between 2 servers. The sender and receiver don't have to be up at the same time.
- joshu 14y agoNit: Google's RPC is not Protocol Buffers. That's just a serialization they use.
- ironchef 14y agoI understand you want nobody on your lawn...and i'm sure newsql/nosql is just IMS again...and you have an opinion that either functional or OOP sucks. They're all tools / approaches. In general, each has several perfectly valid applications. I've used RPC in the past and it was a great approach (a fairly standard XML-RPC interface). Would it have been better as REST with JSON? Probably...at the time REST and JSON didn't exist (late 90s). It certainly felt better than CORBA. From a naive perspective of someone greater than 25, bridge looks interesting. I would expect some (not all) others who have "been there" would feel the same. I don't think the hyperbolic condescending attitude is really called for. I apologize if I'm inferring incorrectly the tone of your post. EDIT: corrected a typo
- mcguire 14y agoRPC is one of the few things that qualifies for my Big List o' Evil. It's not that it doesn't work at all; that would a completely different issue. The problem is that it seems to make a lot of things simpler, right up to the point where it forces a massive amount of its own complexity on you. RPC is not a "leaky abstraction"; it is semantically invalid. It makes network messaging look like function calls of some style. But they aren't. (At some point, you will find yourself asking what happens when the remote procedure completes successfully, but the calling side gets an error. Or spend some time wondering why some simple code is so slow before you realize that it's spending a millisecond on network transmission to do a tiny fraction of that time's computation.) If you ever see the claim that you can write your code normally and then decide how to distribute it, run away screaming. Or picture me doing it for you. It doesn't work. When you build a distributed system, the fact that it is distributed, and how it is distributed, are an order of magnitude more important than everything else. If you're using it to make communicating between languages easier, then yes, that is a big win. But there are other ways to do that. REST and JSON are relatively new, but textual protocols like HTTP and its figurative ancestor, SMTP, aren't. And if that's not good, there's always IETF block diagrams and network byte order. But, you're saying, I'm doing RPC right, structuring my systems around the communications and relying only on large-grained, asynchronous calls. That's great, but what exactly is RPC buying you at that point? 'Cause it's costing you at least visibility into the communications. My first question for anyone using bridge is this: what happens when you have 3 clients calling code on a server, which in turn is calling a couple of other servers, and those servers are making calls back to the original server.