Ever since the SDN hype started, vendors and pundits were quick to tell us how the SDN controllers (and programmers) will replace the traditional networking engineers.
In 2012 I thought there’s no need to worry about that happening in foreseeable future, and not much has changed since then (apart from the obnoxious never-ending should networking engineers become programmers debate).
In related news:
- CCIE certification is still relevant (in 2022), and Cisco introduced DevNet certification
- While MP-TCP got into limited production, we still haven’t solved the major problems of the TCP/IP protocol stack
- In 2021 Hype Cycle, Gartner declared OpenFlow-based SDN dead before reaching plateau
The current explosion of SDN hype (further fueled by recent VMworld announcement of Software-Defined Data Centers) made some networking engineers understandably nervous. This is the question I got from one of them:
I have 8 plus years in Cisco, have recently passed my CCIE RS theory, and was looking forward to complete the lab test when this SDN thing hit me hard. Do you suggest completing the CCIE lab looking at this new future of Networking?
However, as I recently collected a few magic graphs for a short keynote speech, let me reuse them to illustrate this particular challenge we’re all facing. Starting with the obvious, here’s the legendary Diffusion of Innovations: every idea is first adopted by a few early adopters, followed by early and late majority.
Networking in general is clearly in the late majority/laggards phase. What’s important for our discussion is the destruction of value-add through the diffusion process. Oh my, I sound like a freshly-baked MBA whiz-kid, let’s reword it: as a technology gets adopted, more people understand it, the job market competition increases, and thus it’s harder to get a well-paying job in that particular technology area. Supporting Windows desktops might be a good example.
As a successful technology matures, it moves through the four parts of another magic matrix (this one from Boston Consulting Group).
Initially every new idea is a great unknown, with only a few people brave enough to invest time in it (CCIE R&S before Cisco made it mandatory for Silver/Gold partner status). After a while, the successful ideas explode into stars with huge opportunities and fat margins (example: CCIE R&S a decade ago, Nicira-style SDN today… at least for Nicira’s founders), degenerates into a cash cow as the market slowly gets saturated (CCIE R&S is probably at this stage by now) and finally (when everyone starts doing it) becomes an old dog not worth bothering with.
Does it make sense to invest into something that’s probably in a cash cow stage? The theory says “as much as needed to keep it alive”, but don’t forget that CCIE R&S will likely remain very relevant a long time:
- The protocol stacks we’re using haven’t changed in the last three decades (apart from extending the address field from 32 to 128 bits), and although people are working on proposals like MP-TCP, those proposals are still in experimental stage;
- Regardless of all the SDN hoopla, neither OpenFlow nor other SDN technologies address the real problems we’re facing today: lack of session layer in TCP and the use of IP addresses in application layer. They just give you different tools to implement today’s kludges.
- Cisco is doing constant refreshes of its CCIE programs to keep them in the early adopters or early majority technology space, so the CCIE certification is not getting commoditized.
- If you approach the networking certifications the right way, you’ll learn a lot about the principles and fundamentals, and you’ll need that knowledge regardless of the daily hype.
Now that I’ve mentioned experimental technologies – don’t forget that not all of them get adopted (even by early adopters). Geoffrey Moore made millions writing a book that pointed out that obvious fact. Of course he was smart enough to invent a great-looking wrapper – he called it Crossing the Chasm.
The crossing the chasm dilemma is best illustrated with Gartner Hype Cycles (oh my, there’s a Gartner reference in my blog post). After all the initial hype (that we’ve seen with OpenFlow and SDN) resulting in peak of inflated expectations, there’s the ubiquitous through of disillusionment. Some technologies die in that quagmire; in other more successful cases we eventually figure out how to use them (slope of enlightenment).
We still don’t know how well SDN will be doing crossing the chasm (according to the latest Gartner’s charts, OpenFlow still hasn’t reached the hype peak - I dread what's still lying ahead of us); we’ve seen only a few commercial products and none of them has anything close to widespread adoption (not to mention the reality of three IT geographies).
Anyhow, since you’ve decided you want to work in networking, one thing is certain: technology will change (whatever the change will be), and it will happen with or without you. At every point in your career you have to invest some of your time into learning something new. Some of those new things will be duds; others might turn into stars. See also Private Clouds Will Change IT Jobs, Not Eliminate Them by Mike Fratto.
Finally, don’t ask me for “what will the next big thing be” advice. Browse through the six years of my blog posts. You might notice a clear shift in focus; it’s there for a reason.