multi-cloud-architecture

Design a vendor-neutral multi-cloud architecture by applying a structured decision framework for cloud-agnostic service selection, migration planning, and cross-provider workload distribution. This approach minimizes provider-specific dependencies while optimizing for portability across AWS, Azure, and GCP.

Cloud-agnostic architecture patterns integrate compute, storage, and database services across providers without relying on proprietary features. You need these patterns for multi-cloud workloads requiring geographic distribution, disaster recovery, or migration planning across provider boundaries.

Yes, you can use Terraform or OpenTofu to implement multi-cloud infrastructure. The Skill provides IaC guidance and cross-provider tooling references to help translate architecture decisions into reproducible infrastructure code across AWS, Azure, and GCP.

The best way to select cloud services for a web app is using a structured decision framework that evaluates compute, storage, and database options across AWS, Azure, and GCP. This ensures minimal provider-specific dependencies and optimized cross-provider cost.

Yes, this multi-cloud architecture approach works for disaster recovery and migration planning. It applies cloud-agnostic patterns specifically designed for cross-provider workloads, helping teams distribute geographically and recover across provider boundaries.

You should avoid cloud-agnostic architecture patterns when your workload relies heavily on proprietary provider-specific services that lack cross-provider equivalents. Forcing vendor neutrality in these cases can increase complexity and negate cost-optimization benefits across AWS, Azure, and GCP.