Outages of search providers can create huge amounts of havoc. But can we build functionality into our OSes to mitigate the problems?
As I write this, Google has failwhaled. The cause of the problem was initally presumed to be at the AT&T Tier 1 ISP level, causing huge amounts of packet loss. (EDIT: This ended up being explained as a routing problem by Google) The net effect of this is that it's resulted in a crappy day for a lot of us that depend on GMail and use their Google's search services for just about, well, everything.
Click on the "Read the rest of this entry" link below for more.
When Google goes down, lots of stuff breaks. Not just Google's own apps like GMail and Google Talk, but also applications like Firefox, which use Google as it's default search provider.
Default search providers are easy enough to fix in browsers such as Firefox or Internet Explorer (Which uses Windows Live Search) but it requires manual user intervention. However, other applications use Google and its search services. In the event of an apocalyptic business continuity event for a major search provider like Google, how would we as Internet users get all our search services on all our apps working on an alternate provider quickly?
Obviously, Search Failover would not mitigate major systemic outages such as a Tier 1 ISP issue that would affect multiple search services that use it as a bandwidth provider, but presumably all major search providers are procuring connectivity from more than one Tier 1 ISP.
Do we need Search Provider Failover capabilities in our OSes and devices? Talk Back and Let Me Know.