Software defined technologies didn't just spring up out of nowhere.
History of WAN – Introduction
(This is the first part of a series of posts on the history of WANs.)
Very good expensive WANs have moved from rock solid service on point to point leased circuits that carried real regulatory weight and consequences for reliability to less reliable packet switch technologies with QoS but with substantially weaker SLAs and consequences for failure to meet the SLA. IPSec/SSL VPNs over broadband are good for some data users but the broadband connections they use at remote offices are via providers and networks that have issues with network availability, are frequently oversubscribed, and have unpredictable performance for latency, loss, and jitter. These networks are not reliable enough on their own for most business quality voice and mission critical data needs.
The availability and the amount of bandwidth of broadband have continued expand while the cost per bit continues to be lower. Network applications and users have continued to evolve to be more forgiving of less “than a pin drop” quality service but are ever more demanding for more bandwidth. And they want their access to the internet and the cloud on their own terms with their own devices but on your constrained WAN budget.
The IT team is held accountableIt to the company and the users for their own SLA. In the end, providing for reliable, cost effective WAN services to the enterprise and end users and has shifted from the service provider’s problem to the enterprise IT team themselves. The burden has grown and the odds are less in your favor. How can we change those odds so the enterprise has a higher probable solution for success while still containing costs and improving user access to ever more bandwidth?
Categories: Software Defined WAN (SD-WAN)