When SD-WAN first emerged and became the industry trend, many network engineers quickly declared:
“MPLS is dead.”
“SD-WAN fixes everything.”
But even after a decade, that narrative hasn’t proven true, and it never will.
The reason is simple:
SD-WAN is not a transport.
It is an orchestration layer.
MPLS, on the other hand, is a transport service.
SD-WAN does not replace MPLS by default, it can actually use MPLS as one of its underlay transports. It sits above the transports (MPLS, Internet, LTE, etc.) and intelligently steers traffic across them.
The right solution to choose starts with the business requirement and depends on what you're optimizing for not what's trending.
- does uptime have an SLA?
- is application performance critical to revenue?
- are sites in remote or unstable ISP regions?
- is traffic mostly SaaS and cloud based?
- is security centralized or distributed?
- client needs a predictable performance
- low latency between branches is required
- client needs a carrier-backed SLA
- require private circuit
- controlled routing
- Expensive
- Slow to provision
- Harder cloud breakout
- sites are small
- client is a SMB
- budget is constrained
- traffic is mostly SaaS
- downtime tolerance is reasonable
- fast deployment
- simple design is admired
- No SLA guarantees
- ISP path unpredictability
- Performance variability
- client has many transports which needs orchestration
- applications have different priorities
- client needs centralized policy control
- cloud first architecture is in place
- dynamic steering needed
- application aware routing
- better bandwidth utilization
- integrated security (some vendors)
- Careful planning needed to achieve results
- Operational complexity
- Vendor lock-in
- Added costs
- What is the cost of application unreliability?
- What is the cost of latency to the business?
- What is more preferred? Guaranteed performance or Intelligent adaption?
- Need optimization for stability or flexiblity?
- Is your team ready to operate a policy-driven WAN?
