Tip:
Highlight text to annotate it
X
Effectively the way
software defined networks are going to be
selected is very different than the way traditional
and legacy
networks are selected. We are used to
selecting a network based on pore density, packets per second,
head of line blocking, cut through forwarding or not,
store-and-forward type designs and SDNs are going to be selected very
differently.
Effectively, since the hardware is going to be offered in
a commoditized fashion as well as in a purpose-built,
vendor-specific fashion, we're going to see
that the controller takes a bigger part in how
different organizations select their SDN. And why is that? It's really because
they're going to want to run a specific application on their software defined network.
and for that
specific application, specific type of software-defined
networks may make more sense.
It may make more sense to use a certain type of
white label-based switches and a
very simple controller for running a big data cluster
but it may require a different type of network technology
with more buffering or more advanced functionality to run
an SAP ERP application. Likewise it may be a very special type of
application
if I want a cloud data center which is very dynamic
and very tenant based in the way it allocates resources
that kind of setting may require a different type of SDN. So effectively
purpose-built SDNs are likely the way they were going to see
selection of networking technology and a lot of it is going to lie into the
controller technology itself.