The messy dilemma of cloud operations.
Sep 3 Responsibility for cloud operations is often a political football in enterprises.
Sometimes nobody wants it; it’s a toxic hot potato that’s apparently coated in developer cooties.
Sometimes everybody wants it, and some executives think that control over it are going to ensure their next promotion / a handsome bonus / attractiveness for their next job.
Frequently, developers and the infrastructure & operations (I&O) orgs clash over it.
Sometimes, CIOs decide to just stuff it into a Cloud Center of Excellence team which started out doing architecture and governance, and then finds itself saddled with everything else, too.
Lots of arguments are made for it to live in particular places and to be executed in various ways.
There’s inevitably a clash between the “boring” stuff that is basically lifted-and-shifted and rarely changes, and the fast-moving agile stuff.
And different approaches to IaaS, PaaS, and SaaS.
And and and… Well, the fact of the matter is that multiple people are probably right.
You don’t actually want to take a one-size-fits-all approach.
You want to fit operational approaches to your business needs.
And you maybe even want to have specialized teams for each major hyperscale provider, even if you adopt some common approaches across a multicloud environment.
AWS, is a common split, often correlated closely to Windows-based application environments vs Linux-based application environments.) Ideally, you’re going to be highly automated, agile, cloud-native, and collaborative between developers and operators (i.e.
But maybe not for everything (i.e.
not all apps are under active development).
Plus, once you’ve chosen your basic operations approach (or approaches), you have to figure out how you’re going to handle cloud configuration, release engineering, and security responsibilities.
(And all the upskilling necessary to do that well!) That’s where people tend to really get hung up.
How much responsibility can I realistically push to my development teams.
How much responsibility do they want.
How do I phase in new operational approaches over time.
How do I hook this into existing CI/CD, agile, and DevOps initiatives.
There’s no one right answer.
However, there’s one answer that is almost always wrong, and that’s splitting cloud operations across the I&O functional silos — i.e., the server team deals with your EC2 VMs, your NetApp storage admin deals with your Azure Blobs, your F5 specialist configures your Google Load Balancers, your firewall team fights with your network team over who controls the VPC config (often settled, badly, by buying firewall virtual appliances), etc.
When that approach is taken, the admins almost always treat the cloud portals like they’re the latest pointy-clicky interface for a piece of hardware.
This pretty much guarantees incompetence, lack of coordination, and gross inefficiency.
It’s usually terrible at regardless of what scale you’re at.
Unfortunately, it’s also the first thing that most people try (closely followed by massively overburdening some poor cloud architect with Absolutely Everything Cloud-Related.) What works for most orgs: Some form of cloud platform operations, where cloud management is treated like a “product”. It’s almost an internal cloud MSP approach, where the cloud platform ops team delivers a CMP suite, cloud-enabled CI/CD pipeline integrations, templates and automation, other cloud engineering, and where necessary, consultative assistance to coders and to application management teams.
That team is usually on call for incident response, but the first line for incidents is usually the NOC or the like, and the org’s usual incident management team.
But there are lots of options.
Gartner clients: Want a methodical dissection of pros and cons; cloud engineering
operating, and administration tasks; job roles; coder responsibilities; security integration; and other issues.
Read my new note, “Comparing Cloud Operations Approaches“, which looks at eleven core patterns along with guidance for choosing between them, andmaking a range of accompanying decisions.
Posted in Governance 1 Comment Tags: , operations Tiering self-service by user competence.
Aug 10 A nontrivial chunk of my client conversations are centered on the topic of cloud IaaS/PaaS self-service, and how to deal with development teams (and other technical end-user teams, i.e.
data scientists, researchers, hardware engineers, etc.) that use these services.
These teams, and the individuals within those teams, often have different levels of competence with the clouds, operations, security, etc.
but pretty much all of them want unfettered access.
Responsible governance requires appropriate guidelines (policies) and guardrails, and some managers and architects feel that there should be one universal policy, and everyone — from the highly competent digital business team, to the data scientists with a bit of ad-hoc infrastructure knowledge — should be treated identically for the sake of “fairness”.
This tends to be a point of particular sensitivity if there are numerous application development teams with similar needs, but different levels of cloud competence.
In these situations, applying a single approach is deadly — either for agility or your crisis-induced ulcer.
Creating a structured, tiered approach, with different levels of self-service and associated governance guidelines and guardrails, is the most flexible approach.
Furthermore, teams that deploy primarily using a CI/CD pipeline have different needs from teams working manually in the cloud provider portal, which in turn are different from teams that would benefit from having an easy-vend template that gets provisioned out of a ServiceNow request.
The degree to which each team can reasonably create its own configurations is related to the team’s competence with cloud solution architecture, cloud engineering, and cloud security.
Not every person on the team may have a high level of competence; in fact, that will generally not be the case.
However, the very least, for full self-service there needs to be at least one person with strong competencies in each of those areas, who has oversight responsibilities, acts an expert (provides assistance/mentorship within the team), and does any necessary code review.
If you use CI/CD, you also want automation of such review in your pipeline, that includes your infrastructure-as-code (IaC) and cloud configs, not just the app code; i.e.
a tool like Concourse Labs).
Even if your whole pipeline isn’t automated, review of IaC during the dev stage, and not just when it triggers a cloud security posture management tool (like Palo Alto’s Prisma Cloud or Turbot), whether in dev, test, or production.
Who determines “competence”.
To avoid nasty internal politics, it’s best to set this standard objectively.
Certifications are a reasonable approach, but if your org isn’t the sort that tends to pay for internal certifications or the external certifications (AWS/Azure Solution Architect, DevOps Engineer, Security Engineer, etc.) seem like too high a bar, you can develop an internal training course and certification.
It’s not a bad idea for all of your coders (whether app developers, data scientists, etc.) that use the cloud to get some formal training on creating good and secure cloud configurations, anyway.
(For Gartner clients: I’m happy to have a deeper discussion in inquiry
And yes, a formal research note on this is currently going through our editing process and will be published soon.) Tweet.
Posted in Governance Leave a comment Tags: IaaS, PaaS Hunting the Dread Gazebo of Repatriation.
Jul 27 (Confused by the title of this post.
Read this brief anecdote.) The myth of cloud repatriation refuses to die, and a good chunk of the problem is that users (and poll respondents) use “repatriation” is a wild array of ways, but non-cloud vendors want you to believe that “repatriation” means enterprises packing up all their stuff in the cloud and moving it back into their internal data centers — which occurs so infrequently that it’s like a sasquatch sighting.
A non-comprehensive list of the ways that clients use the term “repatriation” that have little to nothing to do with what non-cloud vendors (or “hybrid”) would like you to believe: Outsourcing takeback. The origin of the term comes from orgs that are coming back from traditional IT outsourcing.
However, we also hear cloud architects say they are “repatriating” when they gradually take back management of cloud workloads from a cloud MSP; the workloads stay in the cloud, though.
Migration pause. Some migrations to IaaS/IaaS+PaaS do not go well.
This is often the result of choosing a low-quality MSP for migration assistance, or rethinking the wisdom of a lift-and-shift.
Orgs will pause, switch MSPs and/or switch migration approaches (usually to lift-and-optimize), and then resume.
Some workloads might be temporarily returned on-premise while this occurs.
SaaS portfolio rationalization. Sprawling adoption of SaaS, at the individual, team, department or business-unit level, can result in one or more SaaS applications being replaced with other, official, corporate SaaS (for instance, replacing individual use of Dropbox with an org-wide Google Drive implementation as part of G-Suite).
Sometimes, the org might choose to build on-premises functionality instead (for instance, replacing ad-hoc SaaS analytics with an on-prem data warehouse and enterprise BI solution).
This is overwhelmingly the most common form of “cloud repatriation”.
Development in the cloud, production on premises.
While the dev/prod split of environments is much less common than it used to be, some organizations still develop in cloud IaaS and then run the app in an on-prem data center in production.
Orgs like this will sometimes say they “repatriate” the apps for production.
The Oops. Sometimes organizations attempt to put an application in the cloud and it Just Doesn’t Go Well.
Sometimes the workload isn’t a good match for cloud services in general.
Sometimes the workload is just a bad match for the particular provider chosen.
Sometimes they make a bad integrator choice, or their internal cloud skills are inadequate to the task.
Whatever it is, people might hit the “abort” button and either rethink and retry in the cloud, or give up and put it on premises (either until they can put together a better plan, or for the long term).
Of course, there are the sasquatch sightings, too, like the Dropbox migration from AWS (also see the five-year followup), but those stories rarely represent enterprise-comparable use cases.
If you’re one of the largest purchasers of storage on the planet, and you want custom hardware, absolutely, DIY makes sense.
(And Dropbox continues to do some things on AWS.) Customers also engage in broader strategic application portfolio rationalizations that sometimes result in groups of applications being shifted around, based on changing needs.
While the broader movement is towards the cloud, applications do sometimes come back on-premises, often to align to data gravity considerations for application and data integration.
None of these things are in any way equivalent to the notion that there’s a broad or even common movement of workloads from the cloud back on-premises, though, especially for those customers who have migrated entire data centers or the vast majority of their IT estate to the cloud.
(Updated with research: In my note for Gartner clients, “Moving Beyond the Myth of Repatriation: How to Handle Cloud Projects Failures”, I provide detailed guidance on why cloud projects fail, how to reduce the risks of such projects, and how — or if — to rescue troubled cloud projects.) Tweet.
Posted in Strategy Leave a comment Tags: , migration, risk Building multicloud expertise.
Jul 16 Building cloud expertise is hard.
Building multicloud expertise is even harder.
By “multicloud” in this context, I mean “adopting, within your organization, multiple cloud providers that do something similar” (such as adopting both AWS and Azure).
Integrated IaaS+PaaS providers are complex and differentiated entities, in both technical and business aspects.
Add in their respective ecosystems — and the way that “multicloud” vendors, managed service providers (MSPs) etc.
often deliver subtly (or obviously) different capabilities on different cloud providers — and you can basically end up with a multicloud katamari that picks up whatever capabilities it randomly rolls over.
You can’t treat them like commodities (a topic I cover extensively in my research note on Managing Vendor Lock-In in Cloud IaaS).
For this reason, cloud-successful organizations that build a Cloud Center of Excellence (CCOE), or even just try to wrap their arms around some degree of formalized cloud operations and governance, almost always start by implementing a single cloud provider but plan for a multicloud future. Successfully multicloud organizations have cloud architects that deeply educate themselves on a single provider, and their cloud team initially builds tools and processes around a single provider — but the cloud architects and engineers also develop some basic understanding of at least one additional provider in order to be able to make more informed decisions.
Some basic groundwork is laid for a multicloud future, often in the form of frameworks, but the actual initial implementation is single-cloud.
Governance and support for a second strategic cloud provider is added at a later date, and might not necessarily be at the same level of depth as the primary strategic provider.
Scenario-specific (use-case-specific or tactical) providers are handled on a case-by-case basis; the level of governance and support for such a provider may be quite limited, or may not be supported through central IT at all.
Individual cloud engineers may continue to have single-cloud rather than multicloud skills, especially because being highly expert in multiple cloud providers tend to boost market-rate salaries to levels that many enterprises and mid-market businesses consider untenable.
(Forget using training-cost payback as a way to retain people; good cloud engineers can easily get a signing bonus more than large enough to deal with that.) In other words: while more than 80% of organizations are multicloud, very few of them consider their multiple providers to be co-equal.
Posted in Governance Leave a comment Tags: CCoE, , IaaS, multicloud Refining the Cloud Center of Excellence.
Jul 13 What sort of org structures work well for helping to drive successful cloud adoption.
Every day I talk to businesses and public-sector entities about this topic.
Some have been successful.
Others are struggling.
And the late-adopters are just starting out and want to get it right from the start.
Back in 2014, I started giving conference talks about an emerging industry best practice — the “Cloud Center of Excellence” (CCOE) concept.
I published a research note at the start of 2019 distilling a whole bunch of advice on how to build a CCOE, and I’ve spent a significant chunk of the last year and a half talking to customers about it.
Now I’ve revised that research, turning it into a hefty two-part note on How to Build a Cloud Center of Excellence: part 1 (organizational design) and part 2 (Year 1 tasks).
Gartner’s approach to the CCOE is fundamentally one that is rooted in the discipline of enterprise architecture and the role of EA in driving business success through the adoption of innovative technologies.
We advocate a CCOE based on three core pillars — governance (cost management, risk management, etc.), brokerage (solution architecture and vendor management), and community (driving organizational collaboration, knowledge-sharing, and cloud best practices surfaced organically).
Note that it is vital for the CCOE to be focused on governance rather than on control.
Organizations who remain focused on control are less likely to deliver effective self-service, or fully unlock key cloud benefits such as agility, flexibility and access to innovation.
Indeed, IT organizations that attempt to tighten their grip on cloud control often face rebellion from the business that actually decreases the power of the CIO and the IT organization.
Also importantly, we do not think that the single-vendor CCOE approaches (which are currently heavily advocated by the professional services organizations of the hyperscalers) are the right long-term solution for most customers.
A CCOE should ideally be vendor-neutral and span IaaS
PaaS, and SaaS in a multicloud world, with a focus on finding the right solutions to business problems (which may be cloud or noncloud).
And a CCOE is not an IaaS/PaaS operations organization — cloud engineering/operations is a separate set of organizational decisions (I’ll have a research note out on that soon, too).
Please dive into the research (Gartner paywall) if you are interested in reading all the details.
I have discussed this topic with literally thousands of clients over the last half-dozen years.
If you’re a Gartner for Technical Professionals client, I’d be happy to talk to you about your own unique situation.
Posted in Governance Leave a comment Tags: CCoE, , Gartner, IaaS, PaaS, research Finally, private cloud identical to public cloud.
Jul 9 Digging into my archive of past predictions… In a research note on the convergence of public and private cloud, published almost exactly eight years ago in July 2012, I predicted that the cloud IaaS market would eventually deliver a service that delivered a full public cloud experience as if it were private cloud — at the customer’s choice of data center, in a fully single-tenant fashion.
Since that time, there have been many attempts to introduce public-cloud-consistent private cloud offerings.
Gartner now has a term, “distributed cloud”, to refer to the on-premises and edge services delivered by public cloud providers.
AWS Outposts deliver, as a service, a subset of AWS’s incredibly rich product porfolio.
Azure Stack (now Azure Stack Hub) delivers, as software, a set of “Azure-consistent” capabilities (meaning you can transfer your scripts, tooling, conceptual models, etc., but it only supports a core set of mostly infrastructure capabilities).
Various cloud MSPs, notably Avanade, will deliver Azure Stack as a managed service.
And folks like IBM and Google want you to take their container platform software to facilitate a hybrid IT model.
But no one has previously delivered what I think is what customers really want: Location of the customer’s choice.
Single-tenant; no other customer shares the hardware/service; data guaranteed to stay within the environment.
Isolated control plane and private self-service interfaces (portal, API endpoints); no tethering or dependence on the public cloud control plane, or Internet exposure of the self-service interfaces.
Delivered as a service with the same pricing model as the public cloud services; not significantly more expensive than public cloud as long as minimum commitment is met.
All of the provider’s services (IaaS+PaaS), identical to the way that they are exposed in the provider’s public cloud regions.
Why do customers want that.
Because customers like everything the public cloud has to offer — all the things, IaaS and PaaS — but there are still plenty of customers who want it on-premises and dedicated to them.
They might need it somewhere that public cloud regions generally don’t live and may never live (small countries, small cities, edge locations, etc.), they might have regulatory requirements they believe they can only meet through isolation, they may have security (even “national security”) requirements that demand isolation, or they may have concerns about the potential to be cut off from the rest of the world (as the result of sanctions, for instance). And because when customers describe what they want, they inevitably ask for sparkly pink unicorns, they also want all that to be as cheap as a multi-tenant solution.
And now it’s here, and given that it’s 2020… the sparkly pink unicorn comes from Oracle.
Specifically, the world now has Oracle Dedicated Regions Cloud @ Customer.
(Which I’m going to shorthand as OCI-DR, even though you can buy Oracle SaaS hosted on this infrastructure) OCI’s region model, unlike its competitors, has always been all-services-in-all-regions, so the OCI-DR model continues that consistency.
In an OCI-DR deal, the customer basically provides colo (either their own data center or a third party colo) to Oracle, and Oracle delivers the same SLAs as it does in OCI public cloud.
The commit is very modest — it’s $6 million a year, for a 3-year minimum, per OCI-DR Availability Zone (a region can have multiple AZs, and you can also buy multiple regions).
There are plenty of cloud customers that easily meet that threshold.
(The typical deal size we see for AWS contracts at Gartner is in the $5 to $15 million/year range, on 3+ year commitments.) And the pricing model and actual price for OCI-DR services is identical to OCI’s public regions.
The one common pink sparkly desire that OCI doesn’t meet is the ability to use your own hardware, which can help customers address capex vs.
opex desires, may have perceived cost advantages, and may address secure supply chain requirements.
OCI-DR uses some Oracle custom hardware, and the hardware is bundled as part of the service.
I predict that this will raise OCI’s profile as an alternative to the big hyperscalers, among enterprise customers and even among digital-native customers.
Prior to today’s announcement, I’d already talked to Gartner clients who had been seriously engaged in sales discussions on OCI-DR; Oracle has quietly been actively engaged in selling this for some time.
Oracle has made significant strides (surprisingly so) in expanding OCI’s capabilities over this last year, so when they say “all services” that’s now a pretty significant portfolio — likely enough for more customers to give OCI a serious look and decide whether access to private regions is worth dealing with the drawbacks (OCI’s more limited ecosystem and third-party tool support probably first and foremost).
As always, I’m happy to talk to Gartner clients who are interested in a deeper discussion.
We’ve recently finished our Solution Scorecards (an in-depth assessment of 270 IaaS+PaaS capabilities), including our new assessment of OCI, and although I can’t share the scores themselves pre-publication (it’ll probably be end of July before our editing team gets it published), myself and my colleagues can discuss our findings now.
Update: The scores are summarized in a publicly-reprinted document now.
Posted in 7 Comments Tags: , IaaS, Oracle Outside help can accelerate cloud journeys.
Jul 8 Note: It’s been a while since I blogged actively, and I’m attempting to return to writing short-form posts on a regular basis.
In my current role within Gartner for Technical Professionals, I talk to a lot of cloud architects, engineers, and other technical individual contributors who are concerned that seeking outside assistance for cloud implementations will lead to long-term outsourcing, lack of self-sufficiency, lack of internal cloud skills, and loss of control.
(The CIOs I talk to may have similar concerns, although typically more related to CIO-level concerns about outsourcing.) Those concerns are real, but getting expert outside assistance — from a cloud managed service provider (MSP), consultancy / professional services provider / systems integrator, or even an individual contractor — doesn’t have to mean a sliding down a slippery slope into cloud helplessness.
Things I’ve learned over the past 5+ years of client conversations: Use of expert external assistance accelerates and improves cloud adoption.
Organizations can strongly benefit from expert assistance.
Such assistance reduces implementation times, raises implementation quality, lowers implementation costs as well as long-term total cost of ownership, and provides a better foundation for the organization to enhance its cloud usage in the future.
Low-quality external assistance can have a devastating impact on cloud outcomes.
Choosing the wrong vendor can be highly damaging, resulting in wasted resources, and failure to achieve either the expected business or technical outcomes.
There must be a skills transition plan in place.
Unless the organization expects to outsource cloud operations or application development over the long term, the MSP or consultancy must be contractually obligated to transfer knowledge and skills to the organization’s internal employees.
This transfer must occur gradually, over a multi-month or even multi-year period.
It is insufficient to do a “handoff” at the end of the contract.
The organization needs to shift into a new mode of working as well as gain cloud competence, and this is best done collaboratively, with the external experts handing over responsibilities on a gradual basis.
The organization needs to retain responsibility for cloud strategy and governance.
It is dangerous for organizations to hand over strategic planning to an external vendor, as it is unlikely that plans produced by an external party will be optimally aligned to the organization’s business needs.
For similar reasons, the organization also needs to retain responsibility for governance, including the creation of policy.
An external party may be able to provide useful advice and implementation assistance, but should not be allowed to make strategy or policy decisions.
You can cut years off your migration efforts, and significantly accelerate getting your foundations laid (building a Cloud Center of Excellence, etc.) by getting the right entity to do at least some of it with you, rather than doing all of it for you.
Posted in Strategy 1 Comment Tags: , MSP Gartner’s cloud IaaS assessments, 2019 edition.
Jul 30 We’ve just completed our 2019 evaluations of cloud IaaS providers, resulting in a new Magic Quadrant , Critical Capabilities , and six Solution Scorecards — one for each of the providers included in the Magic Quadrant.
This process has also resulted in fresh benchmarking data within Gartner’s Cloud Decisions tool.
A SaaS offering available to Gartner for Technical Professionals clients
which contains benchmarks and monitoring results for many cloud providers.
As part of this, we are pleased to introduce Gartner’s new Solution Scorecards, an updated document format for what we used to call In-Depth Assessments.
Solution Scorecards assess an individual vendor solution against our recently-revised Solution Criteria (formerly branded Evaluation Criteria).
They are highly detailed documents — typically 60 pages or so, assessing 265 individual capabilities as well as providing broader recommendations to Gartner clients.
The criteria are always divided into Required, Preferred, and Optional categories — essentially, things that everyone wants (and where they need to compensate/risk-mitigate if something is missing), things that most people want but can live without or work around readily, and things that are use case-specific.
The Required, Preferred, and Optional criteria are weighted into a 4:2:1 ratio in order to calculate an overall Solution Score.
2019 Scores If you are a Gartner for Technical Professionals client
the scorecards are available to you today.
You can access them from the links below (Gartner paywall): Amazon Web Services.
Google Cloud Platform.
Oracle Cloud Infrastructure.
Alibaba Cloud International (English-language offerings available outside of China).
We will be providing a comparison of these vendors and their Solution Scorecards at the annual “Cloud Wars” presentation at the Gartner Catalyst conference — one of numerous great reasons to come to San Diego the week of August 11th (or Catalyst UK in London the week of September 15th).
Catalyst has tons of great content for cloud architects and other technical professionals involved in implementing cloud computing. Note that we are specifically assessing just the integrated IaaS+PaaS offerings — everything offered through a single integrated self-service experience and on a single contract.
Also, only cloud services count; capabilities offered as software, hosting, or a human-managed service do not count.
Capabilities also have to be first-party.
Also note that this is not a full evaluation of a cloud provider’s entire portfolio.
The scorecards have “IaaS” in the title, and the scope is specified clearly in the Solution Criteria.
For the details of which specific provider services or products were or were not evaluated, please refer to each specific Scorecard document.
All the scores are current as of the end of March, and count only generally-available (GA) capabilities.
Because it takes weeks to work with vendors for them to review and ensure accuracy, and time to edit and publish, some capabilities will have gone beta or GA since that time; because we only score what we’re able to test, the evaluation period has a cut-off date.
After that, we update the document text for accuracy but we don’t change the numerical scores.
We expect to update the Solution Scorecards approximately every 6 months, and working to increase our cadence for evaluation updates.
This year’s scores vs.
last year’s When you review the scores, you’ll see that broadly, the scores are lower than they were in 2018, even though all the providers have improved their capabilities.
There are several reasons why the 2019 scores are lower than in previous years.
(For a full explanation of the revision of the Solution Criteria in 2019, see the related blog post .) First, for many feature-sets, several Required criteria were consolidated into a single multi-part criterion with “table stakes” functionality; missing any part of that criterion caused the vendor to receive a “No” score for that criterion (“Yes” is 1 point; “No” is zero points; there is no partial credit).
The scorecard text explains how the vendor does or does not meet each portion of a criterion.
The text also mentions if there is beta functionality, or if a feature was introduced after the evaluation period.
Second, many criteria that were Preferred in 2018 were promoted to Required in 2019, due to increasing customer expectations.
Similarly, many criteria that were Optional in 2018 are now Preferred.
We introduced some brand-new criteria to all three categories as well, but providers that might have done well primarily on table-stakes Required functionality in previous years may have scored lower this year due to the increased customer expectations reflected by revised and new criteria.
Customizing the scores The solution criteria, with all of the criteria detail, is available to all Gartner for Technical Professionals clients, and comes with a spreadsheet that allows you to score any provider yourself; we also provide a filled-out spreadsheet with each Solution Scorecard so you can adapt the evaluation for your own needs.
The Solution Scorecards are similarly transparent on which parts of a criterion are or aren’t met, and we link to documentation that provides evidence for each point (in some cases Gartner was provided with NDA information, in which case we tell you how to get that info from the provider). This allows you to customize the scores as you see fit.
Thus, if you decide that getting 3 out of 4 elements of a criteria is good enough for you, or you think that the thing they miss isn’t relevant to you, or you want to give the provider credit for newly-released capabilities, or you want to do region-specific scoring, you can modify the spreadsheet accordingly. If you’re a Gartner client and are interested in discussing the solution criteria, assessment process, and the cloud providers, please schedule an inquiry or a 1-on-1 at Catalyst.
We’d be happy to talk to you.
Posted in Leave a comment Tags: , Gartner, GTP, IaaS, MQ, .
Research Updating Gartner’s cloud IaaS evaluation criteria
Jul 30 In February of this year, .
We revised the Evaluation Criteria for Cloud IaaS (Gartner paywall)
The evaluation criteria (now rebranded Solution Criteria) are essentially the sort of criteria that prospective customers typically include in RFPs.
They are highly detailed technical criteria, along with some objectively-verifiable business capabilities (such as elements in a technical support program, enterprise ISV partnerships, ability to support particular compliance requirements, etc.).
The Solution Criteria are intended to help cloud architects evaluate cloud IaaS providers (and integrated IaaS+PaaS providers such as the hyperscale cloud providers), whether public or private, or assess their own internal private cloud.
We are about to publish Solution Scorecards (formerly branded In-Depth Assessments) for multiple providers; Gartner analysts assess these solutions hands-on and determine whether or not they have capabilities that meet the requirements of a criterion.
The TL;DR version In summary, we revised the Solution Criteria extensively in 2019, and the results were as follows: The criteria have been updated to reflect the current IaaS+PaaS market.
Expectations are significantly higher than in previous years.
Expectations have been aligned to other Gartner research, taking into account customer wants and needs in the relevant market, not just in a cloud-specific context.
Many capabilities have been consolidated and are now required.
Most vendor scores in the Solution Scorecards have dropped dramatically since last year, and there is a much broader spread of vendor scores.
The Evolution of Customer Demands The Evaluation Criteria (EC) for Cloud IaaS was first published in 2012.
It received a significant update every other year (each even-numbered year) thereafter.
When first written, the EC reflected the concerns of our clients at the time, many of whom were infrastructure and operations (I&O) professionals with VMware backgrounds.
With each iteration, the EC evolved significantly, yet incrementally.
In the meantime, the market moved extremely quickly.
The market evolution towards cloud integrated IaaS and PaaS (IaaS+PaaS) providers, and the market exit (or strategic de-investment) of many of the “commodity” providers, radically changed the structure and nature of the market over time.
Cloud IaaS providers weren’t just expected to provide “hardware infrastructure”, but also “software infrastructure”, including all of the necessary management and automation.
This essentially forced these providers into introducing services that compete in many IT markets and in an extraordinary number of software niches.
Furthermore, as the market matured, the roles and expectations of our clients also evolved significantly.
The focus shifted to enterprise-wide initiatives, rather than project-based adoption.
Digital business transformation elevated the importance of cloud-native workloads, while IT transformation emphasized the need for high-quality cloud migration of existing workloads.
The notion that a cloud IaaS provider could successfully run all, or almost all, of a customer’s IT became part of the assumptions that needed to underpin the provider evaluation process. Today’s cloud IaaS customers have high expectations.
Experienced customers are becoming more sophisticated, but late adopters also have high expectations of a provider that have to be met to help the customer overcome barriers to adoption.
For 2019, we decided to take a look at the EC“from scratch”, in order to try to construct a list of criteria that are the most relevant to the initiatives of customers today.
In many cases, our clients are trying to pick a primary strategic IaaS provider.
In other cases, our clients already have a primary provider but are trying to pick a strategic secondary provider as they implement a multicloud strategy.
Finally, some of our clients are choosing a provider for a tactical need, but still need to understand that provider’s capabilities in detail.
Constructing the Revision The revision needed to keep a similar number of criteria (in order to keep the assessment time manageable and the assessment itself at a readable length) — we ended up with 265 for 2019.
In order to keep the total number of criteria down, we needed to consolidate closely-related criteria into a single criterion.
Many criteria became multi-part as a result.
We tried to consolidate the “table stakes” functionality that could be assumed to be a part of all (or almost all) cloud IaaS offerings, in order to make room for more differentiated capabilities. We tried to be as vendor-neutral as possible.
The evaluation criteria have evolved since the initial 2012 introduction; when we introduced new criteria in the past, we often ended up with criteria requirements that closely mirrored the feature-set of the first provider to offer a capability, since that provider shaped customer expectations.
In this 2019 revision, we tried to go back to the core customer requirements, without concern as to whether cloud provider implementations fully aligned with those requirements — the criteria are intended to reflect what customers want and not what vendors offer . There are requirements that no vendors meet, but which we often hear our clients ask for; in such cases we tried to phrase those requirements in ways that are reasonable and implementable at scale, as it’s okay for the criteria to be somewhat aspirational for the market.
We tried to make sure that the criteria were worded using standard Gartner terms or general market terminology, avoiding vendor-specific terms.
(Note that because vendors not-infrequently adopt Gartner terms
there were cases where providers had adopted terminology from earlier versions of EC, and we made no attempt to alter such terms.) We tried to keep to requirements, without dictating implementation, where possible.
However, we had to keep in mind that in cloud IaaS, where there are customers who want fine-grained visibility and control over the infrastructure, there still must be implementation specificity when the customer explicitly wants those elements exposed.
Defining the Criteria During the process of determining the criteria, we sought input broadly within Gartner, both in terms of discussing the criteria with other analysts as well as incorporating things from existing Gartner written research.
(And the criteria reflect, as much as possible, the discussions we’ve had with clients about what they’re looking for, and what they’re putting into their RFPs.) In some cases, we needed input from specialists in a topic.
In some areas of technology, clients who need to have deep-dive discussions on features may talk almost exclusively to analysts specialized in those areas.
Those analysts are familiar with current requirements as well as the future of those technology areas, and are thus the best source for determining those needs.
For example, areas such as machine learning and IoT are primarily covered by analysts with those specializations, even when the customers are implementing cloud solutions.
There are also areas, such as Security, where we have detailed cloud recommendations from those teams.
So we extensively incorporated their input.
We also looked at non-cloud capabilities when there were market gaps relative to customer desires.
There are areas where either cloud providers do not currently have capabilities, or where those capabilities are relatively nascent.
Thus, we needed to identify where customers are using on-premises solutions, and want cloud solutions.
We also needed to determine what the “minimum viable product” should be for the purposes of constructing a criterion around it.
Feedback from non-cloud analysts was also important because it identified areas where clients were not using a cloud solution because of something that was missing.
In many cases, these were not technology features, but issues around transparency, or the lack of solutions acceptable on a global basis.
Finally, the way that customers source solutions, build applications, and manage their data is changing.
We tried to ensure that the new criteria aligned with these trends.
Because more and more of our clients are deploying cloud solutions globally, every criterion also had some requirements as to its global availability.
These are used only for advisory purposes and are not part of scoring. The vendors were allowed to give feedback on the criteria prior to publication.
We wanted to check if the criteria were reasonable, and seemed fair.
We incorporated feedback that constituted good, vendor-neutral suggestions that aligned to customer requirements.
The End Results When you see the Solution Scorecards, you may be surprised by lower scores on the part of many of the providers.
We’re being transparent about the Evaluation Criteria (Solution Criteria) revision in order to help you understand why the scores are lower.
The lower scores were an unintentional side-effect of the revision, but reflect, to some degree, the state of the market relative to the very high expectations of customers.
Note that this year’s lower scores do not indicate that providers have “gone backwards” or removed capabilities; they just reflect the provider’s status against a raised bar of customer expectations. We expect that when we update the scorecards in the second half of this year, scores will increase, as many of the vendors have since introduced missing capabilities, or will do so by the next update. We retain confidence that the solution criteria are a good reflection of a broad range of current customer expectations.
Because many vendors are doing a good job of listening to what customers and prospects want, and planning accordingly, we think that the solution criteria will also be reflected in future vendor roadmaps and market development.
We discuss the Solution Scorecards and scores in a separate blog post.
Posted in 1 Comment Tags: , Gartner, GTP, IaaS, MQ, research Transitioning roles at Gartner.
Jun 19 I’m excited to announce that, as of yesterday, .
I’ve joined the Gartner for Technical Professionals (GTP) team here at Gartner
For years, I’ve enjoyed working closely with Kyle Hilgendorf, Eli Khnaser, Mindy Cancila, Doug Toombs, Marco Meinardi, Alan Waite, and many others in our GTP research division, and I’m looking forward to deepening this collaboration.
Those of you who have known me for a while might remember that I spent more than 15 years in Gartner’s Technology and Service Provider division, and then, for the last two and a half years, I’ve been in the Infrastructure Strategies team in Gartner’s IT Leaders group.
Throughout all of these years, I’ve written a lot of deep-dive research for both managerial and technical audiences, and spent a lot of time talking to everyone from the CIO to the sourcing managers and engineers in the trenches, as well as vendors and investors.
I’ve always enjoyed being more hands-on, though, and the move into GTP will give me a chance to write more in-depth practical advice.
For the next couple of months, I’ll be in a state of transition.
I’ll be doing both types of inquiry for a while, but in the future, .
Clients will need a Gartner GTP “seat” to speak with me
In the next month or two, you’ll see me publish a bunch of research into the ITL agendas, as I finish up that work, and then rethink my previously-planned agenda (much of which will still likely be published, albeit into GTP).
I’ll be at the Gartner Catalyst conference in August
with my first GTP presentation, called “Improve Cloud Operations with Site Reliability Engineering”, focused on how to take the principles, practices, and tools used to manage massive cloud-native applications, and apply them at an enterprise level for cloud operations at a more typical scale.
The cloud IaaS team at Gartner is exceptionally collaborative across our divisions and teams, and I expect to continue working very closely with all the awesome analysts that I’ve worked with over the years.
Gartner is backfilling my previous role, and I highly encourage any cloud IaaS experts out there to reach out to me if you’re interested.
Here’s the job req: https://bit.ly/2JBagOb Tweet.
Posted in Analyst Life, .
Uncategorized 4 Comments Tags: Gartner ← Older Posts
Categories Select Category Analyst Life (39) Applications (3) Gadgets (2) Gaming (6) Governance (4) Industry (107) Infrastructure (210) Marketing (13) Personal (3) Strategy (2) Uncategorized (2).
Jesse Freund on.
Michael Liebow on.
Blog at WordPress.com.
Send to Email Address Your Name Your Email Address.