SDN is slowly matriculating into the enterprise and we estimate there are now over 1,000 production deployments. To date, feedback from early adopters has been surprisingly positive. The software generally works as advertised, and early implementers have been given the white-glove treatment by vendors. In fact, the biggest issue to date has been cultural/organizational. However, as we start to cross the chasm to mainstream implementations, there will be some problems.
To date, we’ve run across just a very small number of actual SDN disasters. One in particular that stands out is a failed bake-off, but it was at very large scale (25,000+ VMs) which isn’t exactly a mainstream scenario. The only publicly reported SDN “issue” I’ve run across was this article here. So overall, not enough data points to draw concrete conclusions.
That said, we’re looking to publish research on SDN failures, to identify pitfalls that enterprises should avoid. So, please let us know of any, and these can include both production and non-production implementations (i.e., failed “bakeoffs”). If you know of any, please reach out via email or Twitter, or leave a comment…
Read Complimentary Relevant Research
Top Strategic Predictions for 2018 and Beyond: Pace Yourself, for Sanity's Sake
Technology-based innovation arrives faster than most organizations can keep up with. Before one innovation is implemented, two others...
View Relevant Webinars
Channel Trends 2017: Three Activities to Focus on
Widespread digital transformation and shifting buyer expectations are placing demands on technology provider channel leaders to enhance...
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.