Cloud Computing
Multi-Cloud and Hybrid
Spotify runs its backend primarily on Google Cloud but uses AWS CloudFront for CDN and Route 53 for DNS. Goldman Sachs operates workloads across AWS, Azure, and on-premises simultaneously. Multi-cloud is not about avoiding vendor lock-in at any cost - it is about using the best tool for each workload within the constraints of team expertise and regulatory requirements.
- Dropbox built Magic Pocket (self-managed storage) to avoid S3 costs at scale while keeping AWS for compute - saving hundreds of millions annually.
- JPMorgan Chase runs latency-sensitive trading on-premises and analytics/ML on AWS and Azure - hybrid driven by regulatory, latency, and cost requirements.
- Walmart uses Anthos to deploy the same Helm charts to both on-premises data centers and Google Cloud without modification.
Terraform Multi-Cloud
**Terraform Multi-Cloud** is a foundational pattern in Multi-Cloud and Hybrid. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Terraform Multi-Cloud is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
What is the primary operational benefit of Terraform Multi-Cloud?
Anthos
**Anthos** is a foundational pattern in Multi-Cloud and Hybrid. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Anthos is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
What is the primary operational benefit of Anthos?
Azure Arc
**Azure Arc** is a foundational pattern in Multi-Cloud and Hybrid. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Azure Arc is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
What is the primary operational benefit of Azure Arc?
Portability Strategy
**Portability Strategy** is a foundational pattern in Multi-Cloud and Hybrid. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Portability Strategy is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
Multi-Cloud and Hybrid is primarily a theoretical concern - real teams just use managed services and ignore architectural patterns
Managed services reduce operational burden but do not eliminate the need for sound architectural decisions about failure modes, scaling, and cost
Managed services handle undifferentiated heavy lifting (patching, backups, failover) but the choice between them, their configuration, and their integration patterns still require deep architectural understanding.
What is the primary operational benefit of Portability Strategy?
Summary
- **Terraform multi-cloud:** HCL with provider plugins for AWS, GCP, Azure, and SaaS services - one tool for all infrastructure with state stored in S3/GCS
- **Anthos:** Google-managed Kubernetes that runs consistently on GKE, AWS EKS, Azure AKS, and on-premises with unified policy and monitoring
- **Azure Arc:** extends Azure management (Policy, Monitor, Defender) to Kubernetes clusters and servers running on AWS, GCP, or on-premises
- **Portability strategy:** compute portability (Kubernetes) is achievable; data service portability (RDS vs Cloud SQL vs Azure SQL) requires abstraction layers or vendor-specific migrations
Related Topics
These topics form the broader Multi-Cloud and Hybrid ecosystem:
- Cloud Architecture Design — Multi-region and multi-cloud share many DR and latency optimization patterns
- Cost Optimization — Multi-cloud arbitrage (using the cheapest provider per service) requires governance overhead that often exceeds the savings
- Microservices in the Cloud — Service mesh (Istio) is the key enabler of multi-cloud microservices - abstracts provider-specific load balancers and DNS
Вопросы для размышления
- How does the architecture for Multi-Cloud and Hybrid change when scaling from 1,000 to 10 million users?
- What are the primary failure modes in a Multi-Cloud and Hybrid system, and what monitoring detects them before users are affected?
- What trade-offs would change the architectural decision for Multi-Cloud and Hybrid in a regulated industry with strict data residency requirements?