An ongoing blog series by our Broadcom Knights, an elite group of Partner Technical Professionals with deep technical expertise in Broadcom’s portfolio and recognized as experts in their field.
Moving Beyond Highly Customised Infrastructures
In my years of designing and deploying vSphere environments across the UK and Europe, I have witnessed a recurring phenomenon: the rise of the “unique snowflake”. Talented engineers – often the most experienced in the room – take immense pride in creating highly tuned, bespoke infrastructure. We love to tinker and tweak advanced settings, layering custom scripts to push the boundaries of what the hypervisor can do. There’s a certain satisfaction in knowing you’ve built the most unique environment in the world. The problem? Nobody else can operate it after you’ve left the room.
On paper, these environments are technical marvels. In practice, they are business liabilities – slow to update, expensive to maintain, and quietly accumulating risk with every undocumented change. The candid truth I’ve had to deliver to more than one customer is this: your “unique requirements” are frequently self-inflicted complexities. Manual customisation feels like high-value work right up until the moment a critical patch is delayed because nobody wants to touch the house of cards. Success with VMware Cloud Foundation (VCF) 9 demands a fundamental mindset shift – from builders of unique machines to providers of standardised, repeatable services.
Unlocking Velocity Through Prescriptive Design
The most immediate benefit of moving away from highly customised infrastructures is deployment velocity – and the numbers are stark. In a traditional manual vSphere setup, racking, cabling, and full-stack assembly across compute, storage, and networking can consume weeks or even months of coordinated effort across multiple IT silos. Projects stall. Momentum dies. And somewhere in a spreadsheet, there’s a parameter worksheet that only one person truly understands.
VCF 9 collapses this timeline through its prescriptive architecture. The new VCF Installer – replacing legacy deployment parameter worksheets and the Cloud Builder appliance – moves the needle from bare metal to a fully functional private cloud in hours, not weeks.
- Hours, not weeks: Automated deployment workflows reduce full-stack deployment time by over 90%.
- Repeatability: Whether spinning up a workload domain in London or Amsterdam, the experience is identical and rubber-stamped.
- Consumption readiness: Because the platform follows a pre-validated design, it is ready for developer consumption almost immediately after the “bring-up” phase.
For the business, this isn’t merely a technical preference – it is a competitive differentiator. I’ve seen this play out first-hand: standardisation enabled us to rapidly build a landing zone cluster for 900 VMs and shut down a legacy Hyper-V data centre, without a linear increase in staff headcount. That’s the kind of outcome that gets infrastructure teams a seat at the strategic table.
Reducing the "Silent Risk" of Configuration Drift
If deployment velocity is the headline win, configuration drift is the slow-burning threat that never makes the headline until it’s too late. Configuration errors are responsible for the majority of IT system outages. In a manually managed estate, identifying and remediating a single misconfiguration can consume six to eight hours of engineering time. Multiply that across a sprawling snowflake infrastructure and you begin to understand why operations teams are perpetually firefighting.
VCF 9 addresses this head-on, making VCF Operations the central management engine and single source of truth. Where host profiles struggled to manage configurations across multiple data centres and environments, VCF 9’s Configuration Templates change the game entirely:
- Desired state templates: We no longer guess what the configuration should be – we define global templates within VCF Operations.
- Scheduled drift detection: The system performs scheduled checks for vCenter and cluster objects, identifying deviations before they impact performance.
- Remediation: If a setting is changed on a whim – like disabling a shell timeout for a quick fix – VCF Operations notices and restores the intended configuration before it becomes a problem.
The shift from reactive troubleshooting to proactive governance is not just operationally cleaner - it fundamentally changes the conversation between infrastructure teams and the business.
Standardisation as a Compliance Power Move
There is a pattern I see repeatedly in customised environments: patching fear. Teams delay critical security updates because they’re worried a patch will break a unique setting – inadvertently creating exactly the kind of security window that threat actors are looking for. The irony is that the very customisation designed to optimise the environment ends up being its greatest vulnerability.
VCF 9 removes this friction by aligning all components into a synchronised, validated release cycle. Security stops being a reactive fire drill and becomes a programmatic reality:
- Zero trust architecture: VCF 9 makes Virtual Private Clouds (VPCs) the standard for workload isolation. NSX micro-segmentation down to the per-vNIC level delivers security that is simply operationally impossible to maintain in a manually configured snowflake environment.
- Predictable security: Security policies follow the workloads automatically, ensuring developer self-service doesn’t lead to security sprawl.
- Sovereignty and compliance: The integrated Security Operations dashboard provides real-time visibility into CVE exposure and compliance scores against standards like CIS or NIST – replacing the ad hoc audits that snowflake environments inevitably require.
Conclusion
Transitioning to VCF 9 requires letting go of the manual, repetitive toil of certificate rotations, password management, and interoperability checking. For engineers who have built their identity around mastering those complexities, that can feel like a loss. I understand that instinct – I’ve felt it myself.
But here’s the reframe: by embracing standardisation, we don’t diminish our expertise – we redirect it. We stop being caretakers of the infrastructure, endlessly cleaning up configuration errors, and start being cloud architects delivering high-value services to the business.
The vision for VCF 9 is to hide the complexity under the hood so the end-user has a frictionless, one-click experience. Think of it like a Ferrari: it’s meant to be driven, not locked in a garage because you’re too afraid to touch the engine. If we cling to our snowflakes, we remain the bottleneck. If we embrace the prescriptive model, we become the engine of business agility.
The snowflake era had its place. VCF 9 is what comes next.