Unified APIs are the future of infrastructure management and reliability engineering. The goal is not more surface area. The goal is less operational fragmentation.
About me
Wesley Morris
Cloud Architect @ VMware by Broadcom
I have 25 years designing SMB and Enterprise IT initiatives to make business outcomes the priority. That means more insight, less time. More outputs, less inputs. My work has always centered on a practical goal: simplify complexity without sacrificing engineering integrity.
This site features blog entries illustrating multi-cloud resiliency strategies, a LAB designed to flatten dev and ops into one dashboard, and VCF ONE - a unified API-driven operating model that gives teams one clean control plane across many cloud environments with curated automation workstreams instead of a patchwork of disconnected tools.
Deliberate cloud use
AWS, Azure, and GCP where they add value: burst capacity, recovery patterns, externalized services, and targeted integrations.
Unified APIs are the future of infrastructure management.
VCF ONE is based on a simple premise: unified APIs are the future of infrastructure management and reliability engineering.
Modern enterprises do not need more disconnected consoles. They need a coherent master layer that can unify the systems they already run. VCF ONE is my proof of concept for that model. It aggregates VCF APIs alongside AWS, Azure, and GCP APIs to provide a more unified operational picture across environments.
That includes
- unified inventory management
- unified cost visibility and cost comparison
- operational views across on-prem and public cloud
- Supervisor cluster visibility for on-prem Kubernetes operations
- support for resiliency strategies, including disaster recovery and failover planning
- simplified workflows that make infrastructure easier to reason about at both the platform and service level
For many enterprises, the right answer is not to force everything into pay-as-you-go public cloud consumption. The better model is often to keep active primary workloads on premises, where data control is stronger, performance is predictable, and costs are known.
Public cloud then becomes highly effective where it adds real value: transactional workflows, burst capacity, externalized services, recovery patterns, and targeted integrations.
That balance matters. It allows organizations to use AWS, Azure, and GCP deliberately, while preserving the advantages of an on-prem operating model for core workloads.
This is the type of architecture I want to help make more accessible: disciplined, measurable, and aligned with how enterprises actually need to run.
The throughline is consistent: unify inventory, cost, automation, Kubernetes, resiliency, and failover views so operators can see and act from one coherent model.
