Network architectures will likely have to undergo some fundamental changes. Networks will need to evolve to architectures that require fewer devices, and customers will need to get much higher utilization out of their existing capacity. Budgets aren't growing fast enough.
Why didn't strategies like network functions visualization (NFV) and software-defined networking (SDN) emerge at the same time that compute and storage capacities were being virtualized and delivered through cloud computing?
Bloggers and vendors are saying lots of different things about the relationship between Software Defined Networking (SDN) and Network Function Virtualization (NFV). Some say that they're very very different and some say that one leads to the other. Maybe they're two sides of the same coin.
Brandon Heller is one of the authors of The Controller Placement Problem. In this video, he's going to give an introduction to OpenFlow and what the network engineer needs to know right off the bat about SDN.
In my last post on vendor lock-in, I suggested that the dominant contributor is software. But that's not to say that it is the only contributor. In this lock-in game, vendors and customers are both complicit.
New software terms and product names are being added to our vocabulary every day, and there's no dictionary or standard document to tell us how to write them. That confusion is the reason I decided to start writing a guide.