Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by simonw on Monday March 26, 2012 @02:49PM
(#3758078)
Is RPC an actual technology? I thought it was more of a protocol design pattern.
[ Parent
| on HN ]
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by ajross on Monday March 26, 2012 @03:15PM
(#3758204)
Remote Procedure Call is a design paradigm for synchronous call-and-response network communication. The Sun RPC protocol is an actual technology defined in RFC1057: http://www.ietf.org/rfc/rfc1057.txt
It's not insane, though not terribly relevant in the modern world. The only common technology still using it is NFS.
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by m0th87 on Monday March 26, 2012 @03:39PM
(#3758294)
If you look at the original RPC work by Bruce Nelson [1], it's pretty clear that there's no strict definition of it. I think most would argue that SOAP would be included, which is still pretty common.
1: http://nd.edu/~dthain/courses/cse598z/fall2004/papers/birrel...
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by ajross on Monday March 26, 2012 @04:12PM
(#3758429)
No, that's the ambiguity I was addressing. RPC means two things. The protocol is used, for the most part, only by NFS. The concept is pervasive.
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by cbsmith on Monday March 26, 2012 @04:55PM
(#3758597)
That's ONC RPC. Not the only implementation. XDR is still used in places, though you're right that it isn't widely used.
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by old-gregg on Monday March 26, 2012 @02:59PM
(#3758129)
man callrpc
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes
by tav on Monday March 26, 2012 @03:41PM
(#3758299)
When Youtube refers to Vitess as being RPC-based, they are not referring to Sun RPC (callrpc), but rather to the generic design pattern of exposing service calls over the network. In particular, Vitess makes services callable [-] using either BSON or JSON serialisation over HTTP CONNECT calls.
[-] http://code.google.com/p/vitess/source/browse/go/rpcwrap/