Multi-Cloud Architect
Multi-cloud architects design systems that run across AWS, GCP, and Azure without being captured by any single provider's proprietary services. Their English must be precise enough to write architecture decision records comparing cloud-native offerings and persuasive enough to present cloud cost governance reports to the C-suite. This path builds the vocabulary and communication skills to lead multi-cloud strategy across engineering and business stakeholders.
Topics covered
- Cloud portability
- Vendor lock-in strategy
- Multi-cloud cost governance
- Cloud-agnostic design
- FinOps
- Architecture decision records
Vocabulary spotlight
4 terms every Multi-Cloud Architect should know in English:
Dependence on a single cloud provider's proprietary services that makes migration costly or impractical
"Using managed Kafka rather than a proprietary queue service reduces vendor lock-in significantly."
The ability to move workloads between cloud providers with minimal rework
"We achieve cloud portability by abstracting provider-specific storage APIs behind a common interface."
The charge levied by a cloud provider for data transferred out of its network
"The egress cost of replicating data to our secondary cloud provider was higher than anticipated."
The layer of infrastructure responsible for managing and orchestrating resources, as distinct from the data plane that carries traffic
"We run the control plane on-premises to retain sovereignty over cluster management regardless of provider."
📚 Vocabulary Reference
Key terms organised by category for Multi-Cloud Architects:
Multi-Cloud Strategy
Cost & FinOps
Architecture Patterns
Governance & Compliance
Recommended exercises
Real-world scenarios you'll practise
- Writing an architecture decision record comparing AWS S3, GCP Cloud Storage, and Azure Blob Storage for a multi-cloud data lake.
- Presenting a multi-cloud cost governance report to the CFO — translating cloud spend data into business impact language.
- Facilitating a trade-off discussion with the engineering team: managed services vs. portable open-source alternatives.
- Communicating a cloud provider outage mitigation plan to senior leadership — explaining failover readiness without technical jargon.