@scottalanmiller said in Why I Feel KVM Is the Easiest HyperVisor to Learn the Basics On:
And I think that VMware, through many market changes, is moving more and more into the "small, but better deployment space." Fewer deployments to maintain, but those that remain are better, and I'm sure pay more. Not entirely unlike Microsoft moving customers from perpetual licenses to O365 - it actually decreased their market penetration, by a lot, but it increased revenue and decreased cost. Big wins, but market share went down.
That's where I see Vmware. Market share is shrinking, it's not the go to product any more. But better customers, at higher revenue. That's better for Vmware.
I think though that on-premises workload while not shrinking are not keeping pace with cloud-hosted workloads. Now plenty of those workloads end up on clouds running vSphere, but even those that do not can still end up managed by VMware. VMware is more than vSphere.
NSX-T/VeloCloud runs just fine on Public Cloud, Containers, even KVM etc. I've seen iSCSI from vSAN shared to bare metal Oracle RAC clusters. Airwatch (leading MDM platform) has really nothing to do with vSphere. WaveFront at purchase couldn't even inject metrics from vSphere and it was a while before they added it (It's focused on application telemetry and ML of that datasets). VMware Horizon View can run on Azure, and the CMP products can manage Azure/AWS etc also. CloudHealth provides compliance across all public clouds also. With the Outpost announcement, I will be able to run vSphere, on AWS leased hardware that's installed in my own datacenter and consume EBS volumes into vSAN while layering AWS RDS on top to provide Postgres or Oracle databases as part of a blueprint to a Project Tango application stack for the ultimate multi-vendor meta sandwich... Spending over a billion on R&D, and a few billion on M&A gets you some damn nice toys