http://craphound.com/overclocked/Cory_Doctorow_-_Overclocked...
Now, there may certainly be larger systemic effects over long time periods caused by eg. the death of the company CEO, the loss of new product development, or the complete destruction of the company's market (in, for example, a global thermonuclear apocalypse that sets us back to the stone age). But the tests absolutely do simulate the simultaneous death of 15,000+ employees, destruction of the Mountain View headquarters, and loss of all datacenters, data, and power in the Bay Area, and verify that remote teams can continue the day-to-day operations in such an event.
On the scale of devastation this article is describing, none of Google's servicing being obliterated really matters but I'm personally pretty glad Google is prepared for multiple, massive scale disasters to happen at once.
When the towers went down in 2001, the first business priority of many companies was getting email back online. It's an incredibly important part of a business.
The one thing you should bear in mind about earthquakes is that in many cases the aftershocks make more damage than the main one, because damage accumulates. Which means that critical infrastructure could take weeks to become fully operational.
The search engine that holds the vast majority of the worlds traffic? The search engine that everyone is going to call on minutes after the earthquake to get news, but isn't going to be there so all the other search engines slow to a crawl. If Google search just disappeared for a week there would be a considerable number of businesses go out of business. You see it now in one off cases where a site is delisted and its traffic drops 99%.
That said, Google has datacenters around the nation and the world so that scenario is unlikely.
Perhaps you can, but how many companies are now wholly dependent on Google for their groupware functionality? What happens if you're one of the gaggle of people who make a living off YouTube?
I bet Google could absorb 100% of the emergency evacuation of AWS in a pinch. Remember also that not 100% of services will be moved, and those that are will not be running at 100% capacity - everyone would be suspending their batch/analytics/warehousing jobs that week (or month).
EDIT: Also, lock in would stop all the redshift/dynamo/etc users from migrating, and would limit people to just what they could throw up on GCE/GAE.
There were Wall St firms that literally had to get the military to escort them into Lower Manhattan in the days after to rescue servers, tapes, etc and cobble something together in a satellite office.
No one wants a repeat of that, and you'll notice subsequent disasters like Sandy have barely been a blip for most as a result of policy changes.
At this point basically any major company will/should have procedures in place for "perfect" DR, the ability for everyone to work from home indefinitely (and alternate offices/infrastructure waiting for the few people who need something special, like the special needs of a trading desk), as well as obviously having back up data centers with full replication.
Of course, the infrastructure of the greater Seattle area is going to be trashed, but chances are good that the Redmond and Kirkland campuses of Microsoft and Google respectively would be intact.
Link to the inundation zone predicted for a magnitude 7.3 earthquake on Seattle: http://wa-dnr.s3.amazonaws.com/Publications/ger_ofr2003-14_t... This isn't even "the big one" as the OP describes, much less "the really big one", but it's a rough description of where the flooding will happen. Downtown Seattle (up and left of the word SEATTLE on the map, with streets in a dense diagonal grid) won't be strongly affected, because downtown Seattle is a hill. With an 8.5 or 9.0 earthquake, of course, Seattle will be much worse off, but there's still some hope that Redmond and Kirkland won't get too damaged.
I could imagine hospitals losing access to health records, emergency responders losing access to mapping or route planning software, people losing access to Uber and not being able to get to the hospital because the taxi companies have gone out of business.
Of course all this stuff is supposed to have clean failover, but not all of it has had its mettle tested.
Why is it necessary to prefix/suffix a comment on the article, with an "of course, people will die and that's obviously bad, we don't want people to die, is this enough mentioning of the people dying that we can say something else without you passive aggressively implying I don't care about the people dying?"
I grew up in Central Oregon which is surrounded by fresh (geologically speaking) lava fields. I wonder if the Native Americans that were around when Mt Mazama was turned into Crater Lake worried about the disruption of their Obsidian tool making business.
The loss of life would be sad too. /s
Though of course if headquarters was really wiped off the map, there'd be huge problems with communication, tribal knowledge that only existed in the heads of senior engineers in Seattle, and so forth.
Ultimately it's up to the user: if they're going to put all their eggs in a us-west basket, they're out of luck if the west coast ends up under water.
I'm not sure I see how that really counts as 'more robust'.
Even if most of the employees live, it's likely basic infrastructure will be a disaster for quite a while. Maybe Google would be able to offload ops work to Mountain View, but it seems likely Amazon.com, AWS and Azure would go down, possibly for months. I wonder what the effect would be on the global economy.