Hardware is only one of the problems affecting the speed of network provisioning. There are also other parameters in Software Defined Network. Sometimes, the cloud services and the same related architecture of Software-Defined related to the networking branch (SDN) are not designed properly and it is believed that they can not resolve the problems of network provisioning speed, thus correcting them can improve the speed with which new services can be released on the network.
Hardware Specification and Software Defined Network
Many analysts do not realize that the current slowness with which they are preparing the new network services relates to the actual configuration of these services and not just dependent on the hardware side. Order to make it explicit the problems should be assessed with fairness towards the two aspects. Most of the time it is true that, time that is lost in the network provisioning is directly related to the hardware and this is partly true. The network infrastructure is based on non-conventional devices and are specialized in certain features and this characteristic requires time for the new hardware to be procured, opened, installed and connected when they found the need. All this is a process that is done manually and if the hardware needs occur at an unexpected time, it may happen that to solve the problem of network, even weeks might be needed.
This difficulty leads to fantasize objective towards virtualization and cloud infrastructure, arguing that decoupling the software specialized hardware can solve the problem of supply. The idea is to abstract the software and all its dependencies to allow it to run on any type of hardware. This stance is real if we just want to eliminate the loss of time due to the supply of the necessary hardware. On the other hand, however, to exaggerate the timing of network provisioning there are software configurations and settings for network services, which require some time so that affect the speed of provisioning.
---
It is Not Only the Hardware Which Can Slow Down the Network Provisioning in Software Defined Network
Hardware, even with the use of virtualization, does not benefit the time required for the configuration of network services. Beyond the container, in fact, we always have to do with real network services, which must be set to provide the required amplitude to keep the characteristics of scalability, security and speed of applications towards the right.
This is the nature of application-oriented networking. Each service requires specific settings to ensure that the network is able to provide the correct deployment of applications and it is not uncommon that a TCP stack optimized for an application it is not correct for the another. And yet, how many times it happens that the details of a specific security application does not fit in another? And how many times the routing application designed to provide excellent performance but reveals unacceptable latencies for another app? Rare.
By answering these questions, one will logically realize that it is not just the hardware which can affect the timing of network provisioning, but also the dexterity necessary to configure network services for each individual application, respecting the principle that a single standard configuration does not is valid for all business and consumer app that normally maintains a network.
Each service must be adapted to the needs and it takes time to be used in the configuration software, beyond the virtualization process for the acquisition and provisioning of hardware resources.
