multi-cloud-architecture
Design multi-cloud architectures across AWS, Azure, and GCP
也可從以下取得: wshobson
Avoid vendor lock-in and build resilient cloud systems. This skill provides a decision framework for selecting and integrating services across multiple cloud providers.
下載技能 ZIP
在 Claude 中上傳
前往 設定 → 功能 → 技能 → 上傳技能
開啟並開始使用
測試它
正在使用「multi-cloud-architecture」。 Compare serverless compute options across clouds
預期結果:
AWS Lambda: Event-driven functions with 15-minute timeout, extensive integrations. Azure Functions: Tight Microsoft ecosystem integration, Durable Functions for stateful workflows. GCP Cloud Functions: Simple pricing, native BigQuery integration. Recommendation: Use Lambda for complex event workflows, Azure Functions for Microsoft stacks, Cloud Functions for data pipelines.
正在使用「multi-cloud-architecture」。 Design geo-distributed architecture for global users
預期結果:
Architecture: Use GCP Cloud CDN for static assets, AWS CloudFront for dynamic content, Azure Front Door for API gateway. Deploy stateless services to GKE, AKS, and EKS in nearest regions. Use Cloud Spanner or Cosmos DB for globally distributed data. Route traffic via DNS-based geo-routing with health checks and automatic failover.
安全審計
安全All static analyzer findings are false positives. The SKILL.md file is pure documentation containing markdown tables, text descriptions, and architecture diagrams. No executable code or command injection vectors exist. External command references are documentation text pointing to other files, not actual shell execution.
品質評分
你能建構什麼
Enterprise multi-cloud strategy
Design a cloud strategy that distributes workloads across AWS, Azure, and GCP to reduce vendor dependency and improve negotiating leverage with providers.
Cloud migration planning
Plan and execute migration from one cloud provider to another while minimizing downtime and maintaining service quality.
Disaster recovery architecture
Build resilient systems with disaster recovery capabilities across multiple cloud providers for business continuity.
試試這些提示
I need to deploy a high-availability web application with auto-scaling. Compare the equivalent services across AWS, Azure, and GCP for compute, storage, database, and networking. Recommend the best option for each category based on cost and features.
Design a cloud-agnostic architecture for a microservices application that can run on any cloud provider. Include specific technologies for compute orchestration, data storage, messaging, and monitoring that work consistently across AWS, Azure, and GCP.
Create a disaster recovery architecture using AWS as primary and Azure as secondary. Include database replication strategy, failover automation, RTO/RPO targets, and step-by-step recovery procedures.
We are migrating from AWS to GCP over 6 months. Create a detailed migration plan using the four-phase approach. Include workload assessment criteria, pilot selection, migration sequencing, risk mitigation, and success metrics for each phase.
最佳實務
- Use infrastructure as code (Terraform) to manage resources consistently across all cloud providers
- Design for failure by assuming any single cloud region or provider can become unavailable
- Implement comprehensive monitoring with cloud-agnostic tools like Prometheus and Grafana
避免
- Building tightly coupled architectures that depend on proprietary cloud services without abstraction layers
- Ignoring data transfer costs between cloud providers which can quickly escalate expenses
- Attempting multi-cloud without proper team expertise in each provider leading to operational complexity