When would you recommend a hybrid or multi-cloud strategy, and when is it a mistake?
Whether your architecture decisions start from business drivers like residency, negotiating position, or best-of-breed services, and whether you have the judgment to recommend a single cloud when no driver exists.
Hybrid means pairing on-prem infrastructure with public cloud; multi-cloud means running more than one public provider. I'd only recommend either with a concrete driver: a regulator demanding data residency, a workload pinned to legacy hardware, or one provider's clearly better service: BigQuery for analytics is the classic case. The default for most companies is one primary cloud, because every extra platform multiplies IAM models, networking, and on-call skills. And cross-cloud traffic rides internet egress at roughly $0.09/GB on AWS, so I'd colocate compute with data from day one.
Multi-cloud is a driver, not a default.
- How would you actually run Kubernetes across AWS and GCP with failover?
- Doesn't Kubernetes make the clouds interchangeable?
- How do you keep multi-cloud spend visible and under control?
In the book this question runs three pages: it adds a deep dive with a diagram, a decision framework, a pitfalls table and a worked answer to each follow-up.
