Index of every page on this site: llms.txt
All skills
github avatar

/cloud-design-patterns

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

Cloud design patterns for distributed systems architecture covering 42 industry-standard patterns across reliability, performance, messaging, security, and deployment categories. Use when designing, reviewing, or implementing distributed system architectures.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/cloud-design-patterns

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈71 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈7.6k more on demand in 9 files.

Description uses 3.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈283 characters, or 3.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Cloud Design Patterns

Architects design workloads by integrating platform services, functionality, and code to meet both functional and nonfunctional requirements. To design effective workloads, you must understand these requirements and select topologies and methodologies that address the challenges of your workload's constraints. Cloud design patterns provide solutions to many common challenges.

System design heavily relies on established design patterns. You can design infrastructure, code, and distributed systems by using a combination of these patterns. These patterns are crucial for building reliable, highly secure, cost-optimized, operationally efficient, and high-performing applications in the cloud.

The following cloud design patterns are technology-agnostic, which makes them suitable for any distributed system. You can apply these patterns across Azure, other cloud platforms, on-premises setups, and hybrid environments.

How Cloud Design Patterns Enhance the Design Process

Cloud workloads are vulnerable to the fallacies of distributed computing, which are common but incorrect assumptions about how distributed systems operate. Examples of these fallacies include:

  • The network is reliable.
  • Latency is zero.
  • Bandwidth is infinite.
  • The network is secure.
  • Topology doesn't change.
  • There's one administrator.
  • Component versioning is simple.
  • Observability implementation can be delayed.

These misconceptions can result in flawed workload designs. Design patterns don't eliminate these misconceptions but help raise awareness, provide compensation strategies, and provide mitigations. Each cloud design pattern has trade-offs. Focus on why you should choose a specific pattern instead of how to implement it.


References

Reference When to load
Reliability & Resilience Patterns Ambassador, Bulkhead, Circuit Breaker, Compensating Transaction, Retry, Health Endpoint Monitoring, Leader Election, Saga, Sequential Convoy
Performance Patterns Async Request-Reply, Cache-Aside, CQRS, Index Table, Materialized View, Priority Queue, Queue-Based Load Leveling, Rate Limiting, Sharding, Throttling
Messaging & Integration Patterns Choreography, Claim Check, Competing Consumers, Messaging Bridge, Pipes and Filters, Publisher-Subscriber, Scheduler Agent Supervisor
Architecture & Design Patterns Anti-Corruption Layer, Backends for Frontends, Gateway Aggregation/Offloading/Routing, Sidecar, Strangler Fig
Deployment & Operational Patterns Compute Resource Consolidation, Deployment Stamps, External Configuration Store, Geode, Static Content Hosting
Security Patterns Federated Identity, Quarantine, Valet Key
Event-Driven Architecture Patterns Event Sourcing
Best Practices & Pattern Selection Selecting appropriate patterns, Well-Architected Framework alignment, documentation, monitoring
Azure Service Mappings Common Azure services for each pattern category

Pattern Categories at a Glance

Category Patterns Focus
Reliability & Resilience 9 patterns Fault tolerance, self-healing, graceful degradation
Performance 10 patterns Caching, scaling, load management, data optimization
Messaging & Integration 7 patterns Decoupling, event-driven communication, workflow coordination
Architecture & Design 7 patterns System boundaries, API gateways, migration strategies
Deployment & Operational 5 patterns Infrastructure management, geo-distribution, configuration
Security 3 patterns Identity, access control, content validation
Event-Driven Architecture 1 pattern Event sourcing and audit trails

External Links

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill is a collection of informational Markdown files describing cloud architecture design patterns. It contains no executable code, scripts, or active components, and all external links point to trusted documentation.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    10 files scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 8 months ago
  • Performance
  • Security
  • cloud-architecture
  • distributed-systems
  • design-patterns
  • reliability
  • messaging
  • deployment
  • resilience
  • system-design

README badge

README badge for github/awesome-copilot/cloud-design-patterns

Provides reference material for 42 cloud design patterns spanning reliability, performance, messaging, security, and deployment—technology-agnostic solutions for common distributed systems challenges. Use when architecting workloads to address fallacies of distributed computing, evaluate trade-offs between patterns like Circuit Breaker or CQRS, and align designs with reliability and cost-optimization goals.

Generated from the current SKILL.md.

Are these patterns specific to Azure or cloud-agnostic?
The patterns are technology-agnostic and applicable across Azure, other cloud platforms, on-premises setups, and hybrid environments.
How many patterns does this skill cover?
The skill covers 42 industry-standard patterns organized across seven categories: reliability and resilience, performance, messaging and integration, architecture and design, deployment and operational, security, and event-driven architecture.
When should I use this skill?
Use this skill when designing, reviewing, or implementing distributed system architectures to address common challenges and avoid misconceptions about how distributed systems operate.
Does this skill help with security patterns?
Yes. The skill includes a security category with three patterns covering federated identity, quarantine, and valet key approaches.

Generated from the current SKILL.md. These answers refresh after source changes.