'Cloud-Native' Fail - Virtualization

'Cloud-Native' Fail - Virtualization

Q: Is running a Virtual Machine on a Cloud-vendor's hypervisor 'Cloud-Native'? 🤔

A: No. The industry terminology 'Cloud-Native' refers to architecture design principles and does not refer to a Cloud vendor.


'Cloud-Native' indicates different (modern) architecture design principles as compared to former architectures - Distributed Systems, Midrange, and Mainframe.


Assess from the lens of Virtualization

".. a Cloud-vendor's proprietary/native platform and Virtual Machine hosting service(s) using legacy Distributed Systems architecture hypervisor ..".

An oxymoron to describe the above as 'Cloud-Native'.


'Cloud-vendor-Native'

The above instead is more correctly defined as 'Cloud-vendor-Native' (CvN). CvN more clearly describes a Cloud vendor preference/bias (not architecture).

CvN can be defined as "the primary, secondary, and tertiary preference/bias to consume Cloud(s) vendor's native services".

CvN is the antithesis of Cloud-Native architecture design principles since almost all of the Cloud-vendor's proprietary/native services do not have service affinity to run on other Clouds.

A different post topic, but there is a not surprising absence of thousands of press releases by end customers celebrating their cost savings hosting legacy architecture VMs workloads on Cloud vendor hypervisors. Gartner 5 R's made this obvious that the Cloud cost savings for most enterprises across industries would not come to fruition unless incumbent workload modernization to Cloud-Native architecture happened first.


VMware Replacement to 'Cloud-Native' (architecture) Virtualization

It is an "architecture technology tax" to run VMs on hypervisors; whether in the Cloud or on-prem, when Cloud-Native Virtualization (KubeVirt is the CNCF project started by Red Hat in 2015) affords vast improvements and efficiencies over traditional hypervisors for Virtualization.

VMware replacement presents the opportunity to gain #CloudNative architecture capabilities for Virtualized workloads without having to change the workload.



#OpenShift Virtualization is Cloud-Native (architecture) for Virtualized workloads. The control plane is #Kubernetes and VMs are managed in containers.



#CFO #CEO #CISO #CIO

#TCO #Cybersecurity #Automation #VMware #RedHat #IBM #Optimization

To view or add a comment, sign in

More articles by Stephen McAleer

  • Kubernetes Retires The Virtual Machine Hypervisor

    Motivations are plentiful these days in the hypervisor market. Migrating from one virtualization hypervisor vendor to…

    1 Comment
  • AI success is limited by the constraints of MultiCloud capability delivery.

    An enterprise's #AI capability delivery throughput is directly dependent (constrained / bottleneck) by the enterprise's…

  • Azure Red Hat OpenShift Partner Connect Spotlight

    I had the pleasure of moderating a collaborative webinar (link here) with Microsoft and Red Hat to delve into the…

  • Superior Virtualization

    TL;DR: #VirtualMachine based #applications gain #CloudNativeArchitecture Capabilities such as ..

    3 Comments
  • Add ‘K’ To MEDDPICC?

    For many years companies have aligned a significant percentage of their SG&A resources on ‘global’ and ‘enterprise’…

    1 Comment
  • Virtualization - Time To Act!

    Many industries, like #UtilitiesIndustry and #OilandGasIndustry, are significantly impacted by the #Virtualization…

  • Sales Miss

    #Sales invests considerable finite shareholder resources into #SalesTraining, product training, and GTM #salesplays…

    2 Comments
  • Will The 2020's & 2030s Be Know For ..

    The many harbinger events (i.e.

  • COTSOps - Automation

    This is the fifth article in the COTSOps Ecosystem Optimization Strategy series. Links to the first, second, third, and…

  • COTSOps - Cloud

    This is the fourth in the COTSOps Ecosystem Optimization Strategy series. Links to the first, second, and third…

Others also viewed

Explore content categories