본문으로 건너뛰기
cccskills
무료GitHub에 공개

multi-cloud-architecture

Plan systems across AWS, Azure, GCP, and OCI by comparing services and architecture patterns. Helps guide service selection, disaster recovery, migration planning, and cost decisions while considering ways to reduce dependence on a single provider.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, GCP, and OCI. Use when building multi-cloud systems, avoiding vendor lock-in, or leveraging best-of-breed services from multiple providers.

설치 방법 보기

이럴 때 유용합니다

  • Planning a system across multiple cloud providers
  • Designing disaster recovery in another cloud
  • Comparing cloud services for a workload
  • Planning a phased cloud migration

포함된 파일(3)

  • SKILL.md5.6 KB
  • references/multi-cloud-patterns.md1.0 KB
  • references/service-comparison.md1.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Multi-Cloud Architecture

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

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

AWSAzureGCPOCIUse Case
EC2Virtual MachinesCompute EngineComputeIaaS VMs
ECSContainer InstancesCloud RunContainer InstancesContainers
EKSAKSGKEOKEKubernetes
LambdaFunctionsCloud FunctionsFunctionsServerless
FargateContainer AppsCloud RunContainer InstancesManaged containers

Storage Services

AWSAzureGCPOCIUse Case
S3Blob StorageCloud StorageObject StorageObject storage
EBSManaged DisksPersistent DiskBlock VolumesBlock storage
EFSAzure FilesFilestoreFile StorageFile storage
GlacierArchive StorageArchive StorageArchive StorageCold storage

Database Services

AWSAzureGCPOCIUse Case
RDSSQL DatabaseCloud SQLMySQL HeatWaveManaged SQL
DynamoDBCosmos DBFirestoreNoSQL DatabaseNoSQL
AuroraPostgreSQL/MySQLCloud SpannerAutonomous DatabaseDistributed SQL
ElastiCacheCache for RedisMemorystoreOCI CacheCaching

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
  • Regulated data platforms on OCI
  • 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/OKE)
  • Database: PostgreSQL/MySQL (RDS/SQL Database/Cloud SQL/MySQL HeatWave)
  • Message Queue: Apache Kafka or managed streaming (MSK/Event Hubs/Confluent/OCI Streaming)
  • Cache: Redis (ElastiCache/Azure Cache/Memorystore/OCI Cache)
  • 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 / OCI

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
  • OCI: Pay-as-you-go, annual commitments, burstable/flexible shapes, preemptible instances

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

Related Skills

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Build and review interfaces against WCAG 2.2 accessibility guidelines. Covers keyboard navigation, screen readers that read interface content aloud, accessible forms, mobile support, and display preferences, helping identify and fix barriers to using a website or app.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Audit an interface for accessibility issues
  • Add keyboard navigation and focus management
  • Improve screen reader support for forms
wshobson/agents4.1만2026년 10월 18일 업데이트

Review AI-generated code for problems hidden behind successful runs. Check failure handling, resource cleanup, unusual inputs, nonexistent dependencies, and departures from project conventions to identify missing safeguards before merging or accepting the work as complete.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Audit code after an AI generation session
  • Review an AI-generated pull request before merging
  • Investigate brittle code that appears to work
wshobson/agents4.1만2026년 10월 18일 업데이트

Build Apache Airflow workflows for data pipelines and scheduled jobs. The skill guides task dependencies, retries, waiting for conditions, testing, and deployment, with patterns for tasks that can be safely rerun.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Building scheduled data pipelines
  • Designing task order and dependencies
  • Implementing custom tasks and condition checks
wshobson/agents4.1만2026년 10월 18일 업데이트

Plan and carry out an AngularJS to Angular migration, from choosing a rewrite strategy to converting components, services, and routes. Includes a hybrid approach that runs both frameworks together while individual features are migrated.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning an AngularJS to Angular migration
  • Moving a large app one feature at a time
  • Converting directives into Angular components
wshobson/agents4.1만2026년 10월 18일 업데이트

Identify software protections that hinder inspection, such as debugger detection and obfuscation that makes code harder to understand. Support authorized binary analysis and CTF security challenges with protection findings, bypass strategies, reports, and analysis scripts.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Identify protections in an authorized malware sample
  • Plan analysis of a packed executable
  • Implement debugger detection for a CTF challenge
wshobson/agents4.1만2026년 10월 18일 업데이트

Design and review REST and GraphQL APIs with consistent naming, data structures, error responses, pagination for large result sets, and versioning strategies. Helps teams define shared standards and plan changes that existing clients can adopt gradually.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Designing a new REST or GraphQL API
  • Reviewing API specifications before implementation
  • Establishing shared API design standards
wshobson/agents4.1만2026년 10월 18일 업데이트

wshobson의 스킬 모두 보기

이 스킬의 문제 신고