multi-cloud-architecture

Design multi-cloud architectures by comparing services across AWS, Azure, GCP, and OCI.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill multi-cloud-architecture-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-cloud-architecture
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/multi-cloud-architecture
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill multi-cloud-architecture-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing and integrating services across AWS, Azure, GCP, and OCI is complex, and poor decisions lead to vendor lock-in, inflated costs, and fragile architectures. This Skill provides a decision framework, service comparison tables, and proven patterns for designing multi-cloud systems. ## Core Features & Use Cases - Service Comparison Tables: Maps equivalent compute, storage, and database services across AWS, Azure, GCP, and OCI for informed selection. - Multi-Cloud Patterns: Covers single-provider with DR, best-of-breed, geographic distribution, and cloud-agnostic abstraction patterns. - Migration & Cost Guidance: Provides a four-phase migration strategy and cost optimization tactics including reserved capacity and spot instances. - Use Case: When planning a system that runs analytics on GCP while keeping enterprise workloads on Azure, use this Skill to select equivalent services, design failover, and estimate cost trade-offs. ## Quick Start Ask the AI to design a multi-cloud architecture for a web application that uses GCP for machine learning and AWS for general compute with disaster recovery on Azure.

Frequently Asked Questions about multi-cloud-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a multi-cloud architecture across AWS, Azure, and GCP?

Start by selecting a pattern: single provider with DR, best-of-breed, geographic distribution, or cloud-agnostic abstraction. Then map equivalent services using comparison tables and standardize on portable layers like Kubernetes, PostgreSQL, and Terraform.

What are the equivalent services across AWS, Azure, GCP, and OCI?

For Kubernetes use EKS, AKS, GKE, or OKE; for object storage use S3, Blob Storage, Cloud Storage, or OCI Object Storage; for managed SQL use RDS, SQL Database, Cloud SQL, or MySQL HeatWave. The references directory contains complete comparison tables.

How do I avoid vendor lock-in when using cloud services?

Use cloud-agnostic building blocks: Kubernetes for compute, PostgreSQL for databases, S3-compatible object storage, Redis for caching, and Prometheus/Grafana for monitoring. Manage everything with Terraform or OpenTofu as an infrastructure abstraction layer.

When should I use a multi-cloud strategy versus a single provider?

Multi-cloud fits when you need best-of-breed services, data sovereignty across regions, or disaster recovery on a second provider. Single provider is simpler when team expertise is concentrated and lock-in tolerance is high.

How do I migrate workloads from one cloud provider to another?

Follow four phases: assess current infrastructure and dependencies, run a pilot workload in the target cloud, migrate incrementally with a dual-run period, then optimize costs and adopt cloud-native services.

What are the cost trade-offs of splitting workloads across cloud providers?

Splitting workloads adds egress fees, managed service premiums, and multiple support plans. Offset these with reserved or committed capacity for 30-70% savings, spot instances, right-sizing, and lifecycle policies for storage.