News for hackers. Stuff that matters.
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes by blhack on Monday March 26, 2012 @01:59PM (#3757841)
What's this? Python? Apache? MySQL? But I thought you had to be running beta-release key value stores, esoteric web servers, and experimental programming languages if you wanted to scale!

/s

Re:7 Years Of YouTube Scalability Lessons In 30 Minutes by zmj on Monday March 26, 2012 @02:23PM (#3757956)
Got your experimental programming language:

> Vitess - a new project released by YouTube, written in Go, it’s a frontend to MySQL. It does a lot of optimization on the fly, it rewrites queries and acts as a proxy. Currently it serves every YouTube database request. It’s RPC based.

Re:7 Years Of YouTube Scalability Lessons In 30 Minutes by maukdaddy on Monday March 26, 2012 @02:32PM (#3758003)
Ah yes, but it's using a ~30 year old technology (RPC).
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.
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/

Re:7 Years Of YouTube Scalability Lessons In 30 Minutes by j2labs on Monday March 26, 2012 @02:52PM (#3758092)
I know the rage is async & nonblocking, but putting Python behind Apache is a good way to get predictable performance without concerns for calls that block, since they're mitigated via threads.

Also, it helps to have money since this approach requires more boxes. But as I said, it's very reliable.

Re:7 Years Of YouTube Scalability Lessons In 30 Minutes by orlandu63 on Monday March 26, 2012 @02:09PM (#3757888)
Nope, you just need lots of cash.
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes by joering2 on Monday March 26, 2012 @05:10PM (#3758661)
speaking of - are they profitable yet?
Re:7 Years Of YouTube Scalability Lessons In 30 Minutes by peterwwillis on Monday March 26, 2012 @04:42PM (#3758547)
Fast, cheap, scalable: pick two.

The fastest, easiest, arguably most reliable way to scale is throwing money at it. And apparently it's easier to hire good people who know 20-year old tech rather than 3-year old.