Main Site โ†—
SkillHubSkillHub
SKILLHUB
Back to List

multi-cloud-architecture

by aRustyDev00GitHub

Provides a decision framework for designing applications across AWS, Azure, and GCP. Includes service comparison tables, multi-cloud patterns, cost optimization strategies, and migration steps. Helps teams avoid vendor lock-in and select appropriate services for specific workloads.

Loading...

Output Preview

output_preview.md

Multi-Cloud Architecture Analysis: High-Traffic Web Application

Query Context

Designing a scalable, cost-effective web application backend that can serve global traffic while avoiding vendor lock-in.

Recommended Pattern: Best-of-Breed with Geographic Distribution

Leverage the strongest services from each provider and distribute traffic based on user location.

Service Mapping & Rationale

| Component | AWS | Azure | GCP | Rationale | |-----------|-----|-------|-----|-----------| | Global Load Balancer | CloudFront + ALB | Front Door + Application Gateway | Cloud Load Balancing | All offer global anycast; choose based on existing CDN contracts. | | Primary Compute | EKS (Kubernetes) | AKS (Kubernetes) | GKE (Kubernetes) | Use Kubernetes for cloud-agnostic compute. Enables workload portability. | | AI/ML Features | SageMaker | Azure Machine Learning | Vertex AI | GCP recommended for cutting-edge AI/ML and TPU access if needed. | | Primary Database | Aurora PostgreSQL | Azure Database for PostgreSQL | Cloud SQL for PostgreSQL | AWS Aurora offers superior performance/availability for global apps. | | Object Storage | S3 | Blob Storage | Cloud Storage | All are robust. Standardize on S3-compatible API for portability. | | Global Caching | ElastiCache for Redis | Azure Cache for Redis | Memorystore for Redis | Use Redis for consistency. Deploy in each region. |

Cost Optimization Strategy

  1. Compute: Use Spot Instances (AWS/Azure) / Preemptible VMs (GCP) for stateless, batch, or CI/CD worker nodes in your Kubernetes clusters (savings up to 70%).
  2. Database: Commit to 1-year Reserved Instances / Committed Use Discounts for your primary database instances.
  3. Storage: Implement S3 Intelligent-Tiering / equivalent lifecycle policies to automatically move cold data to cheaper archival tiers.
  4. Data Transfer: Use provider-specific global backbone networks and consider Cloud Interconnect/AWS Direct Connect for predictable egress costs between clouds/regions.

Implementation Roadmap (Phased)

  1. Phase 1 (Foundation): Deploy the Kubernetes cluster (EKS/AKS/GKE) in your primary region using Terraform. Deploy the PostgreSQL database.
  2. Phase 2 (Global Reach): Set up the global load balancer and deploy Kubernetes pods in 2-3 key geographic regions.
  3. Phase 3 (Specialization): Integrate GCP Vertex AI for ML features if required.
  4. Phase 4 (Optimization): Implement cost management tools (AWS Cost Explorer, Azure Cost Management, GCP Billing Reports) and automate scaling policies.

Key Terraform Snippet (Abstraction Layer)

# Example module call for a cloud-agnostic Kubernetes cluster
module "k8s_cluster" {
  source = "terraform-aws-modules/eks/aws"  # or Azure/GCP equivalent module
  # ... common configuration ...
  cloud_provider = var.target_cloud # Variable to switch providers
}

Next Step: For a detailed cost projection, please provide estimated monthly compute hours, storage GB, and data transfer volumes.

Target Audience

Cloud architects, DevOps engineers, and technical leads designing multi-cloud systems or planning cloud migrations

10/10Security

Low security risk, safe to use

9
Clarity
8
Practicality
8
Quality
7
Maintainability
6
Innovation
Cloud
multi-cloudcloud-architectureaws-azure-gcpcloud-migrationcost-optimization
Compatible Agents
Claude Code
Claude Code
~/.claude/skills/
Codex CLI
Codex CLI
~/.codex/skills/
Gemini CLI
Gemini CLI
~/.gemini/skills/
O
OpenCode
~/.opencode/skills/
O
OpenClaw
~/.openclaw/skills/
GitHub Copilot
GitHub Copilot
~/.copilot/skills/
Cursor
Cursor
~/.cursor/skills/
W
Windsurf
~/.codeium/windsurf/skills/
C
Cline
~/.cline/skills/
R
Roo Code
~/.roo/skills/
K
Kiro
~/.kiro/skills/
J
Junie
~/.junie/skills/
A
Augment Code
~/.augment/skills/
W
Warp
~/.warp/skills/
G
Goose
~/.config/goose/skills/
SKILL.md

Multi-Cloud Architecture

Decision framework and patterns for architecting applications across AWS, Azure, and GCP.

Purpose

Design cloud-agnostic architectures and make informed decisions about service selection across cloud providers.

When to Use

  • Design multi-cloud strategies
  • Migrate between cloud providers
  • Select cloud services for specific workloads
  • Implement cloud-agnostic architectures
  • Optimize costs across providers

Cloud Service Comparison

Compute Services

AWSAzureGCPUse Case
EC2Virtual MachinesCompute EngineIaaS VMs
ECSContainer InstancesCloud RunContainers
EKSAKSGKEKubernetes
LambdaFunctionsCloud FunctionsServerless
FargateContainer AppsCloud RunManaged containers

Storage Services

AWSAzureGCPUse Case
S3Blob StorageCloud StorageObject storage
EBSManaged DisksPersistent DiskBlock storage
EFSAzure FilesFilestoreFile storage
GlacierArchive StorageArchive StorageCold storage

Database Services

AWSAzureGCPUse Case
RDSSQL DatabaseCloud SQLManaged SQL
DynamoDBCosmos DBFirestoreNoSQL
AuroraPostgreSQL/MySQLCloud SpannerDistributed SQL
ElastiCacheCache for RedisMemorystoreCaching

Reference: See references/service-comparison.md for complete comparison

Multi-Cloud Patterns

Pattern 1: Single Provider with DR

  • Primary workload in one cloud
  • Disaster recovery in another
  • Database replication across clouds
  • Automated failover

Pattern 2: Best-of-Breed

  • Use best service from each provider
  • AI/ML on GCP
  • Enterprise apps on Azure
  • General compute on AWS

Pattern 3: Geographic Distribution

  • Serve users from nearest cloud region
  • Data sovereignty compliance
  • Global load balancing
  • Regional failover

Pattern 4: Cloud-Agnostic Abstraction

  • Kubernetes for compute
  • PostgreSQL for database
  • S3-compatible storage (MinIO)
  • Open source tools

Cloud-Agnostic Architecture

Use Cloud-Native Alternatives

  • Compute: Kubernetes (EKS/AKS/GKE)
  • Database: PostgreSQL/MySQL (RDS/SQL Database/Cloud SQL)
  • Message Queue: Apache Kafka (MSK/Event Hubs/Confluent)
  • Cache: Redis (ElastiCache/Azure Cache/Memorystore)
  • Object Storage: S3-compatible API
  • Monitoring: Prometheus/Grafana
  • Service Mesh: Istio/Linkerd

Abstraction Layers

Application Layer
    โ†“
Infrastructure Abstraction (Terraform)
    โ†“
Cloud Provider APIs
    โ†“
AWS / Azure / GCP

Cost Comparison

Compute Pricing Factors

  • AWS: On-demand, Reserved, Spot, Savings Plans
  • Azure: Pay-as-you-go, Reserved, Spot
  • GCP: On-demand, Committed use, Preemptible

Cost Optimization Strategies

  1. Use reserved/committed capacity (30-70% savings)
  2. Leverage spot/preemptible instances
  3. Right-size resources
  4. Use serverless for variable workloads
  5. Optimize data transfer costs
  6. Implement lifecycle policies
  7. Use cost allocation tags
  8. Monitor with cloud cost tools

Reference: See references/multi-cloud-patterns.md

Migration Strategy

Phase 1: Assessment

  • Inventory current infrastructure
  • Identify dependencies
  • Assess cloud compatibility
  • Estimate costs

Phase 2: Pilot

  • Select pilot workload
  • Implement in target cloud
  • Test thoroughly
  • Document learnings

Phase 3: Migration

  • Migrate workloads incrementally
  • Maintain dual-run period
  • Monitor performance
  • Validate functionality

Phase 4: Optimization

  • Right-size resources
  • Implement cloud-native services
  • Optimize costs
  • Enhance security

Best Practices

  1. Use infrastructure as code (Terraform/OpenTofu)
  2. Implement CI/CD pipelines for deployments
  3. Design for failure across clouds
  4. Use managed services when possible
  5. Implement comprehensive monitoring
  6. Automate cost optimization
  7. Follow security best practices
  8. Document cloud-specific configurations
  9. Test disaster recovery procedures
  10. Train teams on multiple clouds

Reference Files

  • references/service-comparison.md - Complete service comparison
  • references/multi-cloud-patterns.md - Architecture patterns

Related Skills

  • terraform-module-library - For IaC implementation
  • cost-optimization - For cost management
  • hybrid-cloud-networking - For connectivity

Source: https://github.com/aRustyDev/dotfiles#.ai~plugins~cloud-infrastructure~skills~multi-cloud-architecture

Content curated from original sources, copyright belongs to authors

Grade A
7.6AI Score
Best Practices
Checking...
Try this Skill

User Rating

USER RATING

0UP
0DOWN
Loading files...

WORKS WITH

Claude Code
Claude
Codex CLI
Codex
Gemini CLI
Gemini
O
OpenCode
O
OpenClaw
GitHub Copilot
Copilot
Cursor
Cursor
W
Windsurf
C
Cline
R
Roo
K
Kiro
J
Junie
A
Augment
W
Warp
G
Goose