Mpls vs Sdwan

Traditional multi-protocol label switching (MPLS) wide area networks have one problem: they are only of limited use for cloud applications. Not so Software-Defined WANs (SD-WANs) that use broadband Internet connections. For companies, it therefore makes sense to envisage a gradual transition from MPLS to an SD-WAN.

As before, MPLS connections (Multi-Protocol Label Switching) the heart of many enterprise WANs . However, MPLS only makes sense if applications are provided via a company-owned data center. The situation is different when applications are kept in cloud data centers, such as Software as a Service (SaaS). Cloud data centers are rarely equipped with MPLS links. Rather, users access the local resources via broadband Internet connections. mpls vs sdwan

Another effect of cloud computing is that businesses can leverage cloud resources as needed. If, for example, a new location is opened, employees can quickly get office packages, storage resources and server performance there. Not so with MPLS: T1 / E1 trunks can take up to 45 days to establish a connection. For higher bandwidths, some months can be estimated. In addition, MPLS links are not available at all imaginable locations.

Software as a service dominates
Market research firm Gartner estimates that by 2018, around 80 percent of all companies will prefer to source applications as part of a SaaS model. With an Enterprise WAN based on MPLS, this change is unmanageable. There are also additional issues. One is the high cost. According to calculations of the consulting firm Telegeography, an MPLS connection with 10 Mbps per month costs about $ 2,100. A hybrid network with a 5 Mbps MPLS connection and a 10 Mbps Internet connection costs $ 1,100. At $ 220 a month, the cheap is a redundant broadband Internet infrastructure with two 5-megabit lines.

Comments