Going With the Flow: Google's Secret Switch to the Next Wave of Networking
In early 1999, an associate computer science professor at UC Santa Barbara climbed the steps to the second floor headquarters of a small startup in Palo Alto, and wound up surprising himself by accepting a job offer.
Context & Ripple Effects
The piece frames Google's networking overhaul through an origin story: in early 1999, an associate computer science professor at UC Santa Barbara accepted a job offer from a small Palo Alto startup, seeding the engineering culture that by 2012 had quietly rewired the company's internal network around flow-based, software-defined switching. It answers, at the deepest infrastructure layer, the question Fortune posed back in 2008 about where Google goes next — for a company whose products are all delivered over its own pipes, the network itself becomes the product.
The story traveled fast on release day: GigaOM, Forbes, ZDNet's Between the Lines, and Softpedia all carried versions within hours, and GigaOM's framing — Google's next challenge being to take software-defined networking beyond its own data centers toward consumers — set the agenda the follow-up commentary would argue about.
First-order effects
- Google's own wide-area and data-center networks now run on flow-based software control, freeing the company from any single switch vendor's proprietary management stack and letting it program traffic policy across the fleet centrally.
- Inside Google, network operations shifts from configuring devices one box at a time to writing centralized control software — a change in who holds the keys to the network.
Second-order effects
- Router and switch vendors selling to hyperscale buyers now have a reference customer proving commodity forwarding hardware plus homegrown control software works at Google's scale, undermining the premium priced into integrated hardware-software bundles.
- Rival cloud and search operators face pressure to replicate the architecture or concede an efficiency gap on their largest cost lines after bandwidth and servers.
Third-order effects
- If the pattern holds across the industry, value in networking migrates from integrated switch-and-router appliances to the control-plane software layer, echoing the way virtualization moved value out of dedicated server hardware.
- A standardized protocol like OpenFlow, proven inside one company's private network, points toward networks run as programmable platforms — with regulators and standards bodies eventually forced to treat network behavior as something auditable in code rather than fixed in silicon.
The trend: Networking is following the same commoditization path computing already took, with economic value migrating from proprietary hardware into software-defined control layers.