Private cloud computing has undergone significant evolution in the last ten years, as well. The shared responsibility model is the focus of this blog, which charts the evolution of the Private Cloud. In a previous post, I discussed the evolution of public cloud service models.

Background: In 2011, the National Institute of Standards and Technology (NIST) provided a definition of cloud computing consisting of four deployment models – Public Cloud, Private Cloud, Hybrid Cloud, and Community Cloud – for the first time ever.

The Private Cloud deployment model is defined as a cloud provided for a single organisation and owned, managed, and operated by the organisation or a third party.

Most of the time, the model specifies a single party in charge of overseeing the whole deployment.

Companies’ responsibilities are shifting due to the aggressive expansion of public cloud vendors into the private cloud space. Stacks from the Public Cloud are now moving into Private Cloud.

An overview and guidelines for shared responsibility for the evolving Private Cloud in 2021 will be provided here, especially when compared to responsibility for the traditional Private Cloud as defined by NIST.

Bringing new value to the marketplace is now a competitive differentiator, and market leaders are now organized to deliver on innovation more quickly each time.

Because of the cloud’s centralized nature, faster development and lower costs are possible. Certain applications, on the other hand, cannot be moved to the Public Cloud and must be kept on the Private Cloud for reasons of compliance, latency, or data jurisdiction.

It’s becoming more common for the Public Cloud stack to be extended to the Private Cloud, and cloud service providers are taking on new responsibilities there as well. Newer service models for Private Cloud and the division of responsibilities between application owners and platform providers are discussed in this blog.

When it comes to managing resources, the Private Cloud is no different than managing resources in the Public Cloud.

Managed Hardware Infrastructure as a Service (HIaaS):

In this model, the infrastructure, software service stack, APIs, and service tools are provided by a Public Cloud vendor and installed on the premises of a customer. Managed Hardware Infrastructure as a Service. Because the cloud provider manages both the infrastructure and the service stack, the organisation is only in charge of the stack of applications running on the infrastructure. Using AWS Outpost or Azure Stack Hub/HCI/Edge as an example, public cloud vendors ship, install and manage the infrastructure.

A data center or an edge site can serve as the Private Cloud in this situation. Depending on the service stack provided, the service provider could assume additional responsibilities, such as service layer responsibility.

Control Plane as a Service (CPaaS):

The most widely used Service layer is Managed Kubernetes. Most cloud service providers provide CPaaS (Managed Service Control Plane), which is a service that manages the public cloud’s control plane. The same stack is available for private clouds as well. In this scenario, the service provider manages the Service (k8s) control plane, with the application owner providing some configuration as an option. The infrastructure, on the other hand, is managed by the organization rather than the public cloud provider. The service provider assists the application owner in configuring and managing the data plane. AWS EKS Anywhere, AWS ECS Anywhere, Azure Arc and Google Anthos are a few examples.

In this scenario, an IaaS service from AWS could be used to run Google Anthos as the cloud vendor manages the control plane.


To summarise, the future application landscape will be largely hybrid or multi-cloud in nature. Infrastructure, platforms, and APIs used in enterprise cloud computing will include a wide range of options, including serverless and traditional server apps running in the cloud.