http://venturebeat.com/2009/06/25/micha … st-system/The Internet was built to withstand nuclear attack. That was why it was built in the ’60s in the first place, as a communications system with redundancy built in so that the military could communicate even if one of the nodes went down.
We saw some of that happen today, as news of Michael Jackson’s death spread like wildfire through the Internet. TMZ.com got the scoop about Jackson being sent to the hospital. But the site went down from the surge of traffic. The LA Times reported he was in a coma, but then that site went down too. The LA Times managed to report that Jackson was dead, and then everyone else started buzzing about it. Twitter went down. Keynote Systems, which measures web site performance, said that the following sites all slowed significantly: ABC, AOL, LA Times, CNN Money and CBS. Starting at 230 pm PST, the average load time for a news site slowed from 4 seconds to 9 seconds.
This is not supposed to happen. More than a decade ago, when I was writing about computer servers and Sun Microsystems was advertising itself as “We’re the dot in dotcom,” the hardware vendors were all talking about “utility computing.” Carly Fiorina, then the chief executive of HP, touted “adaptive computing,” where software would automatically route traffic from one overloaded server to another. Sun called its version of utility computing “N1,” after the code name for a project that aimed at rebalancing server loads on the fly. IBM, meanwhile, operated on a vision that it called “on demand.”
So what exactly can we do to make sure encase of a real emergency global or otherwise that the internet doesn't go out for everyone?