Google lifts its skirts
Yesterday was a remarkable day for the small, slightly obsessed band of Google data-center watchers of which I am one. Around each of the company's sprawling server farms is a high metal fence patrolled by a particularly devoted squad of rent-a-cops, who may or may not be cyborgian in nature.
Context & Ripple Effects
Google has spent years as the most watched yet least seen operator in computing: the Washington Post's 2005 profile of the company and the Times of London's 2007 examination of what Google knows about its users both circled the same paradox — enormous scale, almost no visibility into how the machine actually runs. The December 2008 EE Times reporting on how Google's custom-built servers squeeze out traditional vendors showed why the secrecy matters commercially: the server farms themselves are the product.
Nicholas Carr's post lands in an unusually busy week for the company: Google Ventures was announced on March 31, a Gmail Labs search feature shipped, a profile credited one engineer as the force behind Chrome just days after a widely read account of Google beating Microsoft 'with a knife to a gunfight,' and Google reportedly pulled tethering apps from the Android Market — unconfirmed, though attributed to carrier distribution agreements — while pushing hard at corporate IT budgets. Against that backdrop, even a partial lift on data-center operations is a signal about what the company now considers safe to show.
First-order effects
- Outside observers who have tracked Google's facilities only through fences, permits, and power filings gain direct confirmation of details about data-center operations and security, shrinking the information gap between Google and rivals like Microsoft and Yahoo that publish far more about their own infrastructure.
Second-order effects
- Hardware suppliers and OEMs already squeezed by Google's in-house designs face a better-documented picture of what the company builds itself, sharpening the vendor-bypass dynamic EE Times documented in December 2008 and pressuring competitors to justify premium-priced gear against Google's custom approach.
Third-order effects
- If disclosure stays selective — enough to shape the narrative, not enough to give away efficiency advantages — physical facility design hardens into recognized competitive intellectual property, prefiguring an industry where the location and internals of server farms are guarded as closely as source code.
The trend: Hyperscale operators are consolidating around physical infrastructure as a proprietary moat, with disclosure cadence becoming a deliberate communications tool rather than an oversight.