There has been a massive degree of hype in the networking market surrounding SDN – in fact it is currently outpacing “MPLS” in terms of keyword searches on Gartner.com (crrraaaazy considering how widespread MPLS is deployed). Roughly one year ago, we published our SDN taxonomy but to date, nearly all of the SDN deployments have been in really big environments (i.e., Google, cloud service providers and the largest banks). There hasn’t been a ton of adoption in “normal” networks, and there is a decent amount of confusion out there as well.
However, in the fall of 2013, several prominent and trusted IT vendors including VMware, Juniper and Cisco released their SDN (or related) products, while HP enhanced its existing offering. As a result, SDN and related technologies are now much more consumable for mainstream organizations. So, in essence, we’re entering the era of “SDN for the rest of us” – but despite the availability of these SDN product(s), many “normal” folks are still asking questions like:
- What are the key architectures and deployment approaches out there on the market?
- What is the differentiation between vendor solutions?
- Where, how, and when should we start deploying SDN?
- What are the best practices when evaluating and deploying SDN?
In order to address these questions and identify recommended practices around SDN, we published this research last week: Mainstream Organizations Should Prepare for SDN, targeted for the “rest of us”. It answers the questions above and provides a pragmatic yet strategic roadmap to leverage SDN in your organization.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.