cloud-design-patternslisted

# Cloud Design Patterns Use proven distributed-systems patterns to choose safer architectures and surface trade-offs early. - Leverage native parallel subagent dispatch and 200k+ context windows where available. ## When to Use Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below. - You are designing or reviewing a cloud or distributed-system architecture. - A workload has reliability, latency, scaling, messaging, migration, or security concerns. - You need to shortlist patterns before writing an ADR, design doc, or implementation plan. - You want a technology-agnostic pattern discussion before choosing platform services. ## Pattern Selection Workflow 1. State the main workload goal and the main constraint. 2. Identify the top concerns: reliability, performance, messaging, migration, deployment, security, or eventing. 3. Use the concern-to-pattern map below to shortlist candidates. 4. Compare trade-offs instead of looking for a single perfect pattern. 5. Document why the chosen pattern fits the workload better than the obvious alternatives. ## Concern-To-Pattern Map | Concern | Common patterns | Reference | |---------|-----------------|-----------| | reliability and fault tolerance | Bulkhead, Circuit Breaker, Retry, Health Endpoint Monitoring, Saga | [Reliability And Resilience](./references/reliability-resilience.md) | | performance and scale | Cache-Aside, CQRS, Queue-Based Load Leveling, Rate Limiting, Sharding | [