http://blog.whatsapp.com/index.php/2012/01/1-million-is-so-2...
Here is the same in Erlang for reference (from a few years ago, I would be interested to see if there is a more efficient way now):
http://www.metabrew.com/article/a-million-user-comet-applica...
continue with Ruby as backend for audio/video chats...
consider Ruby for streaming podcasts...
etc. etc.
Re-establishing a million connections at once is going to be hard on the network - the million were built up over a period of time previously yet now they're being re-established Big Bang style.
It's more the impact side of the risk equation i'm thinking of than the probability.
EDIT: typo
The positive in the one big machine scenario is that you have potential to take strong efforts to keep it reliable. The advantage in the lots of machines scenario is that there is a better chance you have well tested failover solutions.
It is the combination of impact and risk that I am discussing.