The New Cloud Management Wheel Is Here

By Marco Meinardi in research

This post originally appeared on the Gartner Blog Network.

If you ever wondered what cloud management means and what it encompasses, Gartner has the answer. The newest cloud management framework has just been published as part of the research “Solution Criteria for Cloud Management Tools” (paywall).

Cloud management is made of seven functional areas and five cross-functional attributes. The functional areas are specific to one use case, whereas the cross-functional attributes aim at broader goals that are common to multiple use cases. The outer ring of the “wheel” in the below figure below represents the functional areas, and the inner ring characterizes the cross-functional attributes.

The research also “double clicks” on each category and provides a total of 201 capabilities that organizations should possess to manage public and private clouds. These capabilities are presented in form of requirements, which can be used to evaluate and select cloud management tools. The research comes in form of a toolkit that clients can download and customize to power their request-for-proposals (RFPs) efforts.

Major updates to the research include:

  • Shift from platforms to tools: Although cloud management platforms (CMPs) are still out there, they’re no longer top of mind of clients according to our inquiries. In the last couple of years, we’ve observed the shift of the interest from broad general-purpose platforms to best-of-breed tools that have deeper functionality in a given area.
  • Addition of observability criteria: These days, observability is certainly stealing the spotlight in the monitoring space. We added observability capabilities and adopted the term as part of the category name “Monitoring and Observability.”
  • AI as cross-functional attribute: AI-powered analytics now touches several aspects of cloud management that we made it a cross-functional attribute (the middle ring of the wheel) in addition to the other four: automation, brokerage, governance and life cycle.

Often, organizations purchase a cloud management tool and implement their management strategy solely based on its available capabilities. With this research, we suggest the opposite approach. Define first what you need to manage and then select the tools that can provide you with the functionality you need.

You can access the full research at “Solution Criteria for Cloud Management Tools” (paywall). Should you want to discuss further, feel free to schedule an inquiry call with me by emailing inquiry@gartner.com or through your Gartner representative.

Follow me on Twitter (@meinardi) or connect with me on LinkedIn for further updates on my research. Looking forward to talking to you!

Why Adopting Kubernetes for Application Portability Is Not a Good Idea

By Marco Meinardi in research

This post originally appeared on the Gartner Blog Network.

I often discuss with clients in infrastructure and operations on whether their organizations should adopt Kubernetes to make their applications portable. If you also have this question, the answer is: no.

Actually, the full story: adopt Kubernetes for the many benefits it provides to application development and architecture and get portability as a side effect. But do not make portability your primary driver for adopting the technology. This thesis is well expanded in the document that Richard Watson, Alan Waite and I have crafted during lockdown this spring: “Assessing Kubernetes for Hybrid and Multicloud Application Portability” (paywall).

Kubernetes or not, application portability always comes at a price that you must be willing to pay – the “portability tax”. Gartner’s advice is to make this decision application by application, based on the likelihood that it will be moved in the future, and how fast that needs to happen. In fact, non-portable applications may still be moved, it will just require more time to execute the transformation.

What is the likelihood that applications change infrastructure provider through their lifespan?

Inquiries show that this likelihood is actually very low. Once deployed in a provider, applications tend to stay there. This is due to data lakes being hard – and expensive – to port and, therefore, end up acting as centers of gravity. The figure below shows the Gartner pyramid of portability, which illustrates basic motivations (at the bottom) and more strategic ones (at the top) for designing portable applications.

For each of your application, ask yourself why portability is important to you. Is it to guarantee survivability? To increase your negotiation leverage with the cloud provider? To mitigate vendor lock-in? The higher you are in the pyramid, the least likely it is that you’ll have those needs.

Kubernetes facilitates portability because it helps standardize our software development life cycle and, most importantly, our operating model. However, it also adds management overhead to our organization, it forces us to engage with commercial vendors and to completely rearchitect our applications. Implementing portability with Kubernetes also requires avoiding any dependency that ties the application to the infrastructure provider, such as the use of cloud provider’s native services. Often, these services provide the capabilities that drove us to the cloud in the first place.

In conclusion, the portability tax is high. Make sure to pay it only for applications that truly need it and that are likely to switch infrastructure provider at some point. For all the others, don’t choose Kubernetes on the basis of a universal portability principle, just because it “sounds right”. On the contrary, adopt Kubernetes for agility, scalability and for modernizing your application architectures.

More on this topic in “Assessing Kubernetes for Hybrid and Multicloud Application Portability” (paywall). Should you want to discuss more, feel free to schedule an inquiry call with myself or Alan Waite by emailing inquiry@gartner.com or through your Gartner representative.

Follow me on Twitter (@meinardi) or connect with me on LinkedIn for further updates on my research. Looking forward to talking to you!

My Research on Cloud Cost Management and Optimization Is Now Available For Free!

By Marco Meinardi in research

This post originally appeared on the Gartner Blog Network.

I am proud to announce that my research on cloud cost management and optimization is now available for free at this link. Gartner made this research public to help organizations in this difficult moment of dealing with a global pandemic and economic recession. The research was selected because it speaks to pandemic-driven business priorities such as cloud adoption and cost optimization.

Gartner has been publishing guidance on managing costs of cloud IaaS and PaaS for the last few years. This practice continues to evolve due to new cloud provider capabilities, organizations increasing their cloud maturity and cloud services becoming more complex. Earlier this year, my colleague Traverse Clayton and I published the latest edition of our cost management framework (depicted in the figure below). This update has drawn a lot of interest from clients, because it helps organizations accelerating cloud adoption in a governed fashion, while unlocking cost savings and minimizing the risk of overspending.

The framework describes the technical capabilities that organizations must develop to manage cloud costs successfully. Our guidance has evolved to encompass new aspects of planning, tracking and optimizing public cloud costs on an ongoing basis. Examples of updates included in this edition are:

  • A clearer delineation between “Reduce” and “Optimize.” Reducing costs is about leveraging more cost-effective configurations without impacting the application architecture. These techniques include rightsizing, scheduling and programmatic discounts. Optimizing costs requires implementing architectural changes that drive costs down. For example, moving from compute instances to event-driven serverless function-as-a-service.
  • The addition of techniques to incentivize financial responsibility. Centralized IT does not want to be held accountable for the spend generated by architectural decisions made by other teams, such as application development and DevOps. Therefore, the framework includes more aspects that help “shift left” the budget accountability. These techniques include budget approvals, dedicated dashboards, cost optimization recommendations and the institution of “leader boards” that highlight the most disciplined cloud consumers.
  • The addition of the correlation of cloud costs with business value. Many digital business applications do not have steady budgets. Their cost often varies on the basis of the number of transactions or users that they handle. The framework helps identify business KPIs and calculate their ratio with cloud costs. Monitoring the trends of that ratio allows organizations to manage costs of applications that have variable demand, in relation to the value that organizations receive from cloud services. Furthermore, such approach allows for the measurement of the efficiency of the cloud cost management practice.

Read the complete cloud cost management and optimization research for free at this link. I hope you find it useful and I welcome your feedback at marco.meinardi@gartner.com. Should you also be a Gartner client wanting to discuss this topic in more details, you can schedule an inquiry call with me by emailing inquiry@gartner.com or through your Gartner representative.

Follow me on Twitter (@meinardi) or connect with me on LinkedIn for further updates on my research. Looking forward to talking to you!