SDN, some might say, is nothing more than the separation of network data traffic processing from the logic and rules controlling the flow, inspection, and modification of that data. That separation of control and data planes has implications.
Traditional network hardware such as switches and routers implement these functions in proprietary firmware. SDN might allow the separation of those functions. Some would say the value is increased flexibility and ease of reconfiguration of networks.
Some might say the advantage is lower cost of network operation. And some would note that the concept has much to do with the ability to use commodity hardware rather than dedicated hardware.
In fact, some might argue that, next to "big data," SDN is one of the most "hyped" concepts in information technology or communications networking.
If so, that is because it is hard to pin down precisely what SDN actually is. It's a design principle, not a protocol, not specific set of boxes or software platforms. It's more like the concept of "cloud computing."
But there is no mistaking the reasons why service providers might like the concept: it promises lower-cost hardware investments and more flexible networks that can adapt in real time, or close to it, to changes in requirements or capabilities.
The main advantage of a software defined network is that it no longer consists of dedicated and proprietary boxes with names like: firewall, load balancer, router.
If an organization tomorrow suddenly two times the need for firewall capacity, compared to load balancers, they can just provision other software on their existing hardware.
In addition everything that is controlled by software can be much easier automated than something that is based on hardware.
That also makes more feasible end-user configurations of services, not simply easier service provider reconfiguration of functions.
No comments:
Post a Comment