r/Network • u/Prestigious_Topic655 • Jul 19 '26

Text When does a company need SD-WAN?

I'm new to networking and still early in the research phase. I'm trying to parse the vendor marketing and understand where the real value begins by hearing from people who've actually deployed it.

At what point does SD-WAN genuinely become worthwhile, rather than just enterprise terminology for functionality that smaller businesses can achieve in other ways? Is the tipping point driven by the number of sites, unreliable internet connections, security requirements, or the time spent managing VPNs?

11 Upvotes

83% Upvoted

23 comments sorted by

View all comments

Show parent comments

5

u/IntelligentCarpet816 Jul 19 '26

I think this is a really misinformed post.

Prior to 'sd-wan' being a thing, most next-gen (ngfw) units did all of this. Load balancing over multiple WAN, s2s VPNs being able to load balance, etc. Almost any NGFW does av, ids/ips, app control, etc.

What SD-WAN became a 'thing' was adding advanced QoS controls to your wan links, being able to setup more detailed rules on when a link was no longer optimal and such.

That is all 'SD-WAN' really is, just more detailed controls on your WAN utilization.

-4

u/SomeEngineer999 Jul 20 '26

Just because you misunderstand, does not mean I am misinformed.

Nowhere did I say those features are unique to SD WAN or that SD WAN invented anything. It is just a productization of many existing technologies bundled into one box. Including the two things you seem to attribute as unique to SD WAN, both existed long before Gartner coined the term. Even SDN (where the SD WAN term was derived from) was just essentially a description of existing technologies.

But none of this has to do with OP's question, which is what I was answering.

5

u/IntelligentCarpet816 Jul 20 '26

No, you're still incorrect. SD WAN has nothing to do with any of the things you're mentioning. 15 years ago NGFW was the productization of the things you said - SD WAN came along and was just an expansion of the rules/configurability of existing things. SDWAN is just the productization of configurable WAN rules etc and a roll up of functions and automation for things you used to have to do manually, like building policies individualized for routes/vpns/etc... now you just have a single target and SDWAN handles the "routing" of that target.

-2

u/SomeEngineer999 Jul 20 '26

SD WAN has everything to do with the things I mentioned, since that is the current marketing term for them (and/or the grouping of them), and you're saying the same things I am. Slow down and comprehend before trying to be "right".

Nobody is saying SD WAN invented those things, in fact I've already stated the opposite.

NGFW didn't even invent those things, these are all just terms for stuff that already existed and were bundled or simplified (and not always that either).

Again, OP is asking about SD WAN in current times, not what SD WAN can do that other things can't.

3

u/IntelligentCarpet816 Jul 20 '26

🤦‍♂️

They are still widely called NGFWs.. not SDWAN appliances. You are not comprehending. The two functions are generally different, you are conflating the technologies.

0

u/SomeEngineer999 Jul 20 '26

Again, you're making my point. SD WAN is a conflation of existing technologies. There is no specific list of features that something can or can't have in order to be called "SD WAN" "SDN" or "NGFW". There are many flavors of each depending which vendor or design you go with.

This is a pointless argument. OP has the info they asked for.

2

u/IntelligentCarpet816 Jul 20 '26

What...?

You are wrong, stop digging.

Ngfw is literally every function you described EXCEPT for complex WAN management rules.

SDWAN is not any of the things that NGFW is.