“Negative” views of Broadcom driving thousands of VMware migrations, rival says

The acquisition of VMware by Broadcom has been a hot topic in enterprise IT for over a year, and the news continues to unfold. A recent report highlights that "negative" views of Broadcom are driving thousands of VMware migrations, with a Western Union executive explicitly citing "challenges" in their working relationship with Broadcom. This isn't just a corporate squabble; it has tangible implications for engineering teams grappling with their virtualization and cloud strategies.

TLDR

Broadcom's acquisition of VMware is leading to widespread customer discontent and significant migrations away from VMware products. An executive from Western Union has specifically mentioned "challenges" working with Broadcom, echoing a broader industry sentiment. For engineering teams, this means re-evaluating core infrastructure, exploring alternative hypervisors and cloud platforms, and navigating potential architectural shifts.

The Broadcom Effect: A Catalyst for Infrastructure Re-evaluation

When Broadcom acquired VMware for $61 billion, it wasn't just a change in ownership; it was a seismic shift for the enterprise virtualization landscape. VMware had long been the undisputed leader, a foundational pillar for data centers worldwide. With Broadcom at the helm, a familiar narrative began to emerge, reminiscent of previous Broadcom acquisitions like CA Technologies and Symantec.

The "challenges" cited by the Western Union executive, while not detailed, likely align with the widely reported concerns across the industry:

• Licensing Model Changes: Broadcom swiftly moved to subscription-only models and bundled products, often eliminating perpetual licenses and significantly increasing costs for many customers, especially smaller businesses and those with specific use cases. The shift to a per-core licensing model, even for CPU-limited workloads, has also been a point of contention.
• Support & Product Portfolio Adjustments: Customers have reported concerns about changes to support structures and a perceived de-emphasis on certain products within the VMware portfolio, leading to uncertainty about long-term roadmaps.
• Direct Sales Model: A move away from a broad partner ecosystem to a more direct sales approach for larger accounts has alienated some channel partners and customers.

These factors combine to create an environment where staying with VMware, under Broadcom's management, no longer feels like the default or most strategic option for many organizations. The "rival" in this context – likely a competitor in the virtualization or hyperconverged infrastructure (HCI) space like Nutanix, Red Hat, or even public cloud providers – is naturally positioned to capitalize on this discontent, offering alternative solutions and highlighting the perceived shortcomings of the incumbent. This isn't just FUD; it's a market reaction to real changes impacting IT budgets and operational strategies.

For engineering teams, this means that the stability and predictability previously associated with VMware are now under question. The mandate from leadership might be clear: "Find alternatives, cut costs, reduce risk."

Navigating the Migration: Practical Implications for Engineering Teams

The decision to migrate away from a core infrastructure component like VMware is not trivial. It impacts everything from budget allocation and skill requirements to architectural design and operational procedures. Engineering teams are on the front lines, tasked with understanding the implications and executing the shift.

Here are some practical considerations and implications:

1. Cost vs. Complexity Analysis:

   • Initial Driver: Often, the primary driver for migration is cost reduction due to new VMware licensing.
   • Hidden Costs: However, migrations incur significant costs themselves: new hardware, software licenses for alternatives, labor for planning and execution, and potential downtime. A thorough Total Cost of Ownership (TCO) analysis is essential.
   • Opportunity for Optimization: This is also an opportunity to right-size environments, decommission underutilized VMs, and optimize resource allocation.

2. Evaluating Alternative Platforms:

   • Open Source Hypervisors: KVM (often managed via OpenStack or Proxmox VE) is a strong contender. It offers flexibility, a vibrant community, and avoids vendor lock-in, but often requires more in-house expertise for management and support.
   • Hyperconverged Infrastructure (HCI): Solutions like Nutanix AHV (Acropolis Hypervisor) or Red Hat OpenShift Virtualization (built on KVM and Kubernetes) offer integrated compute, storage, and networking, simplifying management and scaling.
   • Public Cloud: Migrating workloads to AWS EC2, Azure VMs, or GCP Compute Engine is a common path, moving from CapEx to OpEx. This often involves re-platforming or re-architecting applications for cloud-native benefits, but also introduces new considerations around cloud cost management and vendor lock-in (albeit to a different vendor).
   • Containerization & Kubernetes: For suitable applications, containerization with Kubernetes (on bare metal, edge, or cloud) offers significant agility, scalability, and resource efficiency, potentially replacing VMs entirely for certain use cases.

3. Skill Development & Training:

   • A shift in infrastructure demands a shift in skills. Engineers proficient in vSphere, vCenter, and ESXi will need to acquire expertise in KVM, OpenStack, Kubernetes, cloud provider APIs, or specific HCI platforms.
   • Investing in training and certification for new technologies is crucial to ensure a smooth transition and maintain operational efficiency.

4. Application Compatibility & Re-platforming:

   • Not all applications migrate easily. Legacy applications, especially those with tight hardware dependencies or specific licensing requirements tied to VMware, can be challenging.
   • Teams will need to assess each application: "lift-and-shift," "re-platform," or "re-factor." This is a chance to modernize critical applications and retire obsolete ones.

5. Risk Management & Business Continuity:

   • Migration planning must include robust rollback strategies, disaster recovery considerations, and thorough testing.
   • Phased migrations, starting with non-critical workloads, can help minimize risk and build confidence.

This mass migration isn't just a reactive measure; it's an accelerant for modernization. It forces organizations to critically examine their entire infrastructure stack, often leading to more resilient, cost-effective, and agile solutions in the long run.

Key Takeaways

• Broadcom's Impact is Real: The licensing changes and operational shifts under Broadcom are undeniably driving significant migrations away from VMware.
• Opportunity for Alternatives: This creates a fertile ground for alternative hypervisors (KVM, Proxmox), HCI solutions (Nutanix), and public cloud providers to gain market share.
• Engineering Teams on the Front Line: Engineers are tasked with complex migration planning, TCO analysis, and skill acquisition.
• Modernization Catalyst: The migrations offer a strategic opportunity to re-evaluate and modernize entire application portfolios and infrastructure architectures.
• Vendor Lock-in is a Key Lesson: This event underscores the importance of avoiding deep vendor lock-in and maintaining flexibility in infrastructure choices.

The "negative" views of Broadcom aren't just sentiments; they're translating into concrete actions across thousands of enterprises. For developers and engineering teams, this signals a period of significant change and opportunity. The landscape of enterprise virtualization is evolving rapidly, pushing teams to embrace new technologies, hone new skills, and design more resilient, multi-platform infrastructures. The choices made now will define the agility and cost-efficiency of IT operations for years to come.

This article was originally published on ExecuteAI Software. We cover AI news that matters for business.