multi-cloud-architecture

lifangda

Updated Today

59 views

Metadesign

About

This Claude Skill provides a decision framework to design multi-cloud architectures across AWS, Azure, and GCP. It helps developers select and integrate the best services from different providers to avoid vendor lock-in and leverage best-of-breed solutions. Use it when building cloud-agnostic systems, migrating between providers, or optimizing workloads across multiple clouds.

Documentation

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

AWS	Azure	GCP	Use Case
EC2	Virtual Machines	Compute Engine	IaaS VMs
ECS	Container Instances	Cloud Run	Containers
EKS	AKS	GKE	Kubernetes
Lambda	Functions	Cloud Functions	Serverless
Fargate	Container Apps	Cloud Run	Managed containers

Storage Services

AWS	Azure	GCP	Use Case
S3	Blob Storage	Cloud Storage	Object storage
EBS	Managed Disks	Persistent Disk	Block storage
EFS	Azure Files	Filestore	File storage
Glacier	Archive Storage	Archive Storage	Cold storage

Database Services

AWS	Azure	GCP	Use Case
RDS	SQL Database	Cloud SQL	Managed SQL
DynamoDB	Cosmos DB	Firestore	NoSQL
Aurora	PostgreSQL/MySQL	Cloud Spanner	Distributed SQL
ElastiCache	Cache for Redis	Memorystore	Caching

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

Use reserved/committed capacity (30-70% savings)
Leverage spot/preemptible instances
Right-size resources
Use serverless for variable workloads
Optimize data transfer costs
Implement lifecycle policies
Use cost allocation tags
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

Use infrastructure as code (Terraform/OpenTofu)
Implement CI/CD pipelines for deployments
Design for failure across clouds
Use managed services when possible
Implement comprehensive monitoring
Automate cost optimization
Follow security best practices
Document cloud-specific configurations
Test disaster recovery procedures
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

Quick Install

/plugin add https://github.com/lifangda/claude-plugins/tree/main/multi-cloud-architecture

Copy and paste this command in Claude Code to install this skill

GitHub 仓库

lifangda/claude-plugins

Path: cli-tool/skills-library/cloud-infrastructure/multi-cloud-architecture

Related Skills

langchain

Meta

LangChain is a framework for building LLM applications using agents, chains, and RAG pipelines. It supports multiple LLM providers, offers 500+ integrations, and includes features like tool calling and memory management. Use it for rapid prototyping and deploying production systems like chatbots, autonomous agents, and question-answering services.

View skill

llamaindex

Meta

LlamaIndex is a data framework for building RAG-powered LLM applications, specializing in document ingestion, indexing, and querying. It provides key features like vector indices, query engines, and agents, and supports over 300 data connectors. Use it for document Q&A, chatbots, and knowledge retrieval when building data-centric applications.

View skill

business-rule-documentation

Meta

This skill provides standardized templates for systematically documenting business logic and domain knowledge following Domain-Driven Design principles. It helps developers capture business rules, process flows, decision trees, and terminology glossaries to maintain consistency between requirements and implementation. Use it when documenting domain models, creating business rule repositories, or bridging communication between business and technical teams.

View skill

project-structure

Meta

This skill provides comprehensive project structure guidelines and best practices for organizing codebases across various project types. It offers standardized directory patterns for monorepos, web frameworks, backend services, and libraries to ensure scalable, maintainable architecture. Use it when designing new project structures, organizing monorepo workspaces, or establishing code organization conventions for teams.

View skill