<img src="https://certify.alexametrics.com/atrk.gif?account=VdU0q1FYxz20cv" style="display:none" height="1" width="1" alt="">

Cloud Consumption Models

In many enterprises today, public cloud consumption is happening in an ad-hoc or varied fashion across several pockets of a large organization. There are two basic consumption models for public cloud resources: With “Cloud Direct”, the end users are communicating directly through cloud-native APIs. With “Cloud Brokered”, a Cloud Management Platform (CMP) is acting as an intermediary between the end users and the public clouds. There are also cases within a single enterprise where both cloud consumption models are used. These various options are illustrated as follows:


vCommander Cloud Consumption Value-add

vCommander adds value regardless of the cloud consumption model. For Cloud Direct, value-add is gained by providing engineering 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, and the ability to perform showback/chargeback along with reactive cost optimizations for cloud expense management.

In the Cloud Brokered case,  additional, more proactive values can be achieved, such as cost/quota enforcement and intelligent workload placement. 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. And over time, more cloud consumption can move from direct to brokered, to fully realize the value of a vCommander.

Next Generation Application Architectures

For next generation application architectures built with micro-services, 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 though the vCommander Service Catalog and API or called directly by applications and operational scripts.

Additionally, there are also many Container and Kubernetes service variants available to the market, both in the public cloud and on-premise.  vCommander was designed to support all of these different variations as it integrates bi-directionally with popular DevOps tools and technologies including Terraform, Cloud Formation Templates, ARM Templates, Jenkins, Git and more. 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 afterwards 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 vCommander benefits when consuming Cloud Direct or Cloud Brokered: