I'm about to enroll for a Network Engineer degree but is

Anyone?

File: ziNh454.jpg (452KB, 1000x709px) Image search: [Google]

452KB, 1000x709px

Bachelors of networking here. SDN is the networking meme right now. If you plan on using it or working with carrier-grade shit, a background in networking will help far more than basics in comp. Sci.

File: narcosa.jpg (341KB, 1376x930px) Image search: [Google]

341KB, 1376x930px

>>61495372
Perhaps I should clarify. To carriers (ISPs and the like) SDNs represent a desperately needed acceleration to any of their issues. Take for instance his long it takes to set up a VXLan on a Linux network. A multitude of coherent commands need to be issued across the networks' entirety. Not only do these commands need to be issued in proper sequence, but they need to keep in mind just what sort of environment each command is run. Imagine doing this in every fiber point in the entirety of a carrier's tier one backbone, and combine with the insane overhead of every special snowflake every L2 and L3 hop along the way. This is why SDNs like OpenDaylight are a thing right now. They keep a single and contiguous view if an entire network, and allow a single API to modify and update that view.

From an IT perspective, it simplifies things enormously. No running to a zillion devices and keeping them in mind as you chart a course through your backbone. Or for Amazon, dynamically assigning networks for every customer under similar circumstances.

Additionally, a business can implement these changes from a single control point at both an incredibly reduced cost, and at a substantially greater speed