We need another IT term, right?
My problem is terms like “Software-Defined Data Center” focus on a very limited “how,” and not the “why.” And far too many of the infrastructure and operations (I&O) teams that I talk to use SDDC to describe how they are modernizing their own data center – and in a very architecturally-specific way. Or, they are talking about turning their entire infrastructure into a “private cloud.” Sorry, that’s missing the mark, by a long shot.
The problem is, many/most of the services that the enterprise needs don’t reside on providers that are architecturally consistent – and the requirements might be very, very different. A single provider and a single architecture makes little sense. So in the end, my I&O team is building a modern data center that can only talk to a limited set of other data centers – if any at all. And far, far too often, I&O organizations are bemoaning the fact that they can’t keep up with cloud providers, and their enterprise is working around them.
That’s because you’re being an obstacle, and not a part of the solution.
Enterprises don’t need a more modern data center. I repeat, enterprises don’t need a more modern data center. They need to to be able to leverage a variety of data centers that support a variety of services, and they need the I&O team to provide support in order to ensure efficient and effective service delivery. The I&O team cannot be defined by the hardware they own and operate.
The I&O team’s responsibilities need to be defined by the data centers and services that the enterprise needs – and not the other way around.
Most enterprises – especially larger – will never eliminate their need for their own data centers. But that’s not the point. Most enterprises – perhaps almost all – will be leveraging many cloud services. So, sorry, our data center is just delivering a part of what our enterprise needs. We can’t let our hardware define us.
So I like the term “Enterprise-Defined Data Center” (EDDC). The enterprise defines what’s needed, not I&O. To enable an EDDC, the I&O team will leverage technologies to enable a software-defined data center, they will use technologies to support aggregation, customization, integration and governance of multiple cloud providers, they will build private clouds for specific services (that will become hybrid and possibly migrate to other providers over time), they will essentially take responsibility for all enterprise services, regardless of the specific provider or data center or architectures being used. Because the enterprise doesn’t and shouldn’t care about those details.
The core competency of I&O must change from being very good providers, to being very good brokers/managers/intermediaries. There’s really no future in hardware-hugging. Very few enterprises can afford to be loyal to just their own data centers. Let the enterprise define their requirements.
Read Complimentary Relevant Research
Cloud Computing Primer for 2017
Cloud has evolved from a disruption to an expected approach to traditional as well as next-generation IT. Our research helps IT leaders,...
View Relevant Webinars
La Strategia SAP: tra In-memory e Cloud Computing
SAP, uno dei più importanti fornitore di software per le organizzazioni italiane, sta attraversando un processo di trasformazione strategica...
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.