Being in and around the VMware space for around 7 years, I
believe it is my inherent responsibility to give “VMware by Broadcom” a chance
to explain why and what happened after the acquisition.
When Broadcom revised the VMware Solution ecosystem, it absolutely
failed to communicate to the customers, the intent and vision behind the transition
to the cloud/platform operating model and we have all witnessed that this definitely created
a big drift in understanding and adoption of this idea.
It has been challenging for all of us to get that mindshare
and the customers also failed to get that transitional momentum. This is due to the fact that the infrastructure is
divided between different teams in most organizations. There is an infrastructure
team, there are developers and designers, the Windows, Unix, Storage, Network,
Network Security, Cybersecurity, monitoring teams and so on.
It is very true that any form of a digital transformation
strategy has a People’s piece and a Process piece to it apart from the obvious Financial
and Technology perspective.
By not being able to corelate the IT Piece to People and the
Process piece, created a certain drift and there you see a lot of blogs and YouTube
videos posting about how VMware is dying after the Broadcom acquisition.
Let’s not forget, VMware is at the very core of many digital
transformation strategies by bringing to the market their most selling product which
all of us know by the name of vSphere.
The customers took vSphere at the center, added the Storage
and Network, wrapped it up with Security and there you go, that is the simplest
expression/definition of any traditional IT Infrastructure.
But, as Customers embarked on their respective digital transformation journeys, they tried to modernize their
infrastructure services and bring cloud methodologies to it. However, due to
the fact that they lacked a lot of Integrations and APIs that were essential to
the delivery of these services, the thought process of modernization did not
flourish well with the traditional 3 Tier architecture. This bought hinderance
in scaling up and innovation.
This big gap between the provisioning and the delivery of
the services using traditional infrastructure led to adoption of Cloud
Migrations strategies and customers rapidly started moving their applications to
public clouds.
We may all agree that the public clouds definitely have the
right architecture in terms of running a Software defined Architecture on x86
hardware. On top of that, by orchestrating and automating the processes, they
allow for the delivery of the consumption layer with much ease.
Migrating to public cloud is not new and while it is so
essential, I want to state some facts.
As per the IDC White Paper - August 2024, 51% customers are concerned with privacy and
39% customers consider cloud migration expensive and complex to manage.
In my personal opinion, the application that are not optimized
for the cloud should never be migrated to the public cloud unless you are
willing to pay heavy bills.
All of what you read above was either factual or my personal
opinion. Now, I will conclude this blog with my understanding about VCF.
With the adoption of VCF, your own IT admins who have been managing
your Virtual Infrastructure till now, will be empowered with the tools they
will require to build, deploy and operate a private cloud infrastructure and
using cloud methodologies as a part of that. They will have tools for capacity
management so that they can operate at scale, not just around On-premise but
globally deployed infrastructure as well. The ability to provide flexibility in
order to Modernize with Security and resilience is what our customers have been
looking for.
