Is it me, or does the network industry remind you of Revenge of the Nerds? Networking was cast aside in the cloud revolution, but now companies are learning -- the painful way – what a mistakes that was. Don’t kid yourself one bit if you think that VMware’s acquisition of Nicirawas mostly about developing heterogeneous hypervisor data centers or reducing networking hardware costs. If you do think that, you’re probably an application developer, hypervisor administrator, or data center architect. You’ve been strutting your newly virtualized self through rows of server racks over the last five year, casually brushing aside the networking administrators. You definitely had some outside support for your views: Google, VMware, and even OpenFlow communities have messaged that networking organizations aren’t cool anymore and need to be circumvented by coding around the network, making it a Layer 2 network or taking over the control plane.
To be fair, though, networking vendors and networking teams helped to create this friction, too, since they built their networks on:
40 years of outdated networking reliability principles. The current state of networking can be in many ways traced back to ARPANET’s principle: a single method to reliably communicate a host of multiple sets of flows, traffic, and workloads. Basically, voice, video, and all applications traverse the same rigid and static set of links that only change when a failure occurs. The package didn’t matter.