In many enterprises today, cloud consumption is happening in an ad-hoc or varied fashion across several pockets of a large organization.
If we boil down how organizations consume cloud resources, there are two basic consumption models:
Cloud Consumption Model #1: Cloud Brokered
On-Prem and/or cloud resources are consumed (e.g. self-service provisioning) and governed through the IT dept.
Cloud Consumption Model #2: Cloud Direct
Cloud consumers are directly consuming resources through APIs, cloud-native tools, consoles, etc. There are also cases within a single enterprise where both cloud consumption models are used.
Cloud Management Platforms: Cloud Consumption Value-Add
A modern cloud management platform adds automation and governance value regardless of how cloud resources are provisioned and accessed.
For Cloud Direct, value-add is gained by providing engineering/DevOps teams with the freedom to consume public cloud resources as needed and preserving overall corporate agility through the use of a single-pane-of-glass across the entire hybrid cloud environment for governance.
In the Cloud Brokered case, additional, more proactive values can be achieved, such as cost/quota enforcement and intelligent placement of new cloud resources following the rules and guardrails defined by IT.
In large organizations, there can be a mix of both Direct and Brokered consumption, depending upon the particular use case and business unit process maturity.
By supporting a direct access model, a CMP can be adopted without disrupting existing processes and developer workflows. And over time, more cloud consumption can move from direct to brokered, to fully realize the value of a cloud management platform
Next Generation Application Architectures
For next-generation application architectures built with microservices, DevOps methodologies, and Kubernetes orchestration, the infrastructure underlying the applications may be provisioned and scaled in an automated manner using APIs referred to as “Infrastructure as code”.
These APIs can also be either brokered through a CMP Service Catalog and API or called directly by applications and operational scripts.
There are also Container and Kubernetes service variants available to the market, both in the public cloud and on-premise.
A CMP like Embotics vCommander is designed to support these different variations as it integrates bi-directionally with popular DevOps tools and technologies including:
- Cloud Formation Templates,
- ARM Templates,
- Git, and more.
A CMP like Embotics vCommander is also Kubernetes distribution independent and agnostic, supporting mainstream services such as Amazon EKS, OpenShift, PKS. AKS, etc.
In the brokered case, policies can be enforced in band at provisioning time. With direct access, policies are validated asynchronously afterward in an advisory manner.
Regardless of the consumption mechanism or resource location, vCommander adds significant value by providing IT visibility and many application governance capabilities across both traditional and cloud-native applications.
The table below highlights the benefits of a cloud management platform when consuming Cloud Direct or Cloud Brokered: