1---2name: cloud-solution-architect-43description: Design well-architected Azure cloud systems — 10 design principles, 6 architecture styles, 44 design patterns, technology choices, WAF pillars4tier: standard5applyTo: '**/architecture*,**/*cloud*,**/*azure-arch*,**/*waf*'6currency: 2026-04-227metadata:8 source: https://skillmd.com/skills/fabioc-aloha/cloud-solution-architect-49---1011# Cloud Solution Architect1213> Design well-architected, production-grade cloud systems following Azure Architecture Center best practices1415---1617## Ten Design Principles for Azure Applications1819| # | Principle | Key Tactics |20|---|-----------|-------------|21| 1 | **Design for self-healing** | Retry with backoff, circuit breaker, bulkhead isolation, health endpoint monitoring, graceful degradation |22| 2 | **Make all things redundant** | Eliminate single points of failure, use availability zones, deploy multi-region, replicate data |23| 3 | **Minimize coordination** | Decouple services, use async messaging, embrace eventual consistency, use domain events |24| 4 | **Design to scale out** | Horizontal scaling, autoscaling rules, stateless services, avoid session stickiness, partition workloads |25| 5 | **Partition around limits** | Data partitioning (shard/hash/range), respect compute & network limits, use CDNs for static content |26| 6 | **Design for operations** | Structured logging, distributed tracing, metrics & dashboards, runbook automation, infrastructure as code |27| 7 | **Use managed services** | Prefer PaaS over IaaS, reduce operational burden, leverage built-in HA/DR/scaling |28| 8 | **Use an identity service** | Microsoft Entra ID, managed identity, RBAC, avoid storing credentials, zero-trust principles |29| 9 | **Design for evolution** | Loose coupling, versioned APIs, backward compatibility, async messaging for integration, feature flags |30| 10 | **Build for business needs** | Define SLAs/SLOs, establish RTO/RPO targets, domain-driven design, cost modeling, composite SLAs |3132---3334## Architecture Styles3536| Style | Description | When to Use | Key Services |37|-------|-------------|-------------|--------------|38| **N-tier** | Horizontal layers (presentation, business, data) | Traditional enterprise apps, lift-and-shift | App Service, SQL Database, VNets |39| **Web-Queue-Worker** | Web frontend → message queue → backend worker | Moderate-complexity apps with long-running tasks | App Service, Service Bus, Functions |40| **Microservices** | Small autonomous services, bounded contexts, independent deploy | Complex domains, independent team scaling | AKS, Container Apps, API Management |41| **Event-driven** | Pub/sub model, event producers/consumers | Real-time processing, IoT, reactive systems | Event Hubs, Event Grid, Functions |42| **Big data** | Batch + stream processing pipeline | Analytics, ML pipelines, large-scale data | Synapse, Data Factory, Databricks |43| **Big compute** | HPC, parallel processing | Simulations, modeling, rendering, genomics | Batch, CycleCloud, HPC VMs |4445### Selection Criteria4647- **Domain complexity** → Microservices (high), N-tier (low-medium)48- **Team autonomy** → Microservices (independent teams), N-tier (single team)49- **Data volume** → Big data (TB+), others (GB)50- **Latency requirements** → Event-driven (real-time), Web-Queue-Worker (tolerant)5152---5354## Cloud Design Patterns (44 Patterns)5556WAF pillar mapping: **R**=Reliability, **S**=Security, **CO**=Cost Optimization, **OE**=Operational Excellence, **PE**=Performance Efficiency.5758### Messaging & Communication5960| Pattern | Summary | Pillars |61|---------|---------|---------|62| **Asynchronous Request-Reply** | Decouple request/response with polling or callbacks | R, PE |63| **Claim Check** | Split large messages; store payload separately, pass reference | R, PE |64| **Choreography** | Services coordinate via events without central orchestrator | R, OE |65| **Competing Consumers** | Multiple consumers process messages from shared queue concurrently | R, PE |66| **Pipes and Filters** | Decompose complex processing into reusable filter stages | R, OE |67| **Priority Queue** | Prioritize requests so higher-priority work is processed first | R, PE |68| **Publisher/Subscriber** | Decouple senders from receivers via topics/subscriptions | R, PE |69| **Queue-Based Load Leveling** | Buffer requests with a queue to smooth intermittent loads | R, PE |70| **Sequential Convoy** | Process related messages in order while allowing parallel groups | R, PE |7172### Reliability & Resilience7374| Pattern | Summary | Pillars |75|---------|---------|---------|76| **Bulkhead** | Isolate resources per workload to prevent cascading failure | R |77| **Circuit Breaker** | Stop calling a failing service; fail fast to protect resources | R |78| **Compensating Transaction** | Undo previously committed steps when a later step fails | R |79| **Health Endpoint Monitoring** | Expose health checks for load balancers and orchestrators | R, OE |80| **Leader Election** | Coordinate distributed instances by electing a leader | R |81| **Retry** | Handle transient faults by retrying with exponential backoff | R |82| **Saga** | Manage data consistency across microservices with compensating transactions | R |83| **Scheduler Agent Supervisor** | Coordinate distributed actions with retry and failure handling | R |8485### Data Management8687| Pattern | Summary | Pillars |88|---------|---------|---------|89| **Cache-Aside** | Load data on demand into cache from data store | PE |90| **CQRS** | Separate read and write models for independent scaling | PE, R |91| **Event Sourcing** | Store state as append-only sequence of domain events | R, OE |92| **Index Table** | Create indexes over frequently queried fields in data stores | PE |93| **Materialized View** | Pre-compute views over data for efficient queries | PE |94| **Sharding** | Distribute data across partitions for scale and performance | PE, R |95| **Static Content Hosting** | Serve static content from cloud storage/CDN directly | PE, CO |96| **Valet Key** | Grant clients limited direct access to storage resources | S, PE |9798### Design & Structure99100| Pattern | Summary | Pillars |101|---------|---------|---------|102| **Ambassador** | Offload cross-cutting concerns to a helper sidecar proxy | OE |103| **Anti-Corruption Layer** | Translate between new and legacy system models | OE, R |104| **Backends for Frontends** | Create separate backends per frontend type (mobile, web, etc.) | OE, PE |105| **Compute Resource Consolidation** | Combine multiple workloads into fewer compute instances | CO |106| **External Configuration Store** | Externalize configuration from deployment packages | OE |107| **Sidecar** | Deploy helper components alongside the main service | OE |108| **Strangler Fig** | Incrementally migrate legacy systems by replacing pieces | OE, R |109110### Security & Access111112| Pattern | Summary | Pillars |113|---------|---------|---------|114| **Federated Identity** | Delegate authentication to an external identity provider | S |115| **Gatekeeper** | Protect services using a dedicated broker that validates requests | S |116| **Quarantine** | Isolate and validate external assets before allowing use | S |117| **Rate Limiting** | Control consumption rate of resources by consumers | R, S |118| **Throttling** | Control resource consumption to sustain SLAs under load | R, PE |119120### Deployment & Scaling121122| Pattern | Summary | Pillars |123|---------|---------|---------|124| **Deployment Stamps** | Deploy multiple independent copies of application components | R, PE |125| **Gateway Aggregation** | Aggregate multiple backend calls into a single client request | PE |126| **Gateway Offloading** | Offload shared functionality (SSL, auth) to a gateway | OE, S |127| **Gateway Routing** | Route requests to multiple backends using a single endpoint | OE |128| **Geode** | Deploy backends to multiple regions for active-active serving | R, PE |129130---131132## Technology Choices133134### Decision Framework135136For each technology area, evaluate: **requirements → constraints → tradeoffs → select**.137138| Area | Key Options | Selection Criteria |139|------|-------------|-------------------|140| **Compute** | App Service, Functions, Container Apps, AKS, VMs, Batch | Hosting model, scaling, cost, team skills |141| **Storage** | Blob Storage, Data Lake, Files, Disks, Managed Lustre | Access patterns, throughput, cost tier |142| **Data stores** | SQL Database, Cosmos DB, PostgreSQL, Redis, Table Storage | Consistency model, query patterns, scale |143| **Messaging** | Service Bus, Event Hubs, Event Grid, Queue Storage | Ordering, throughput, pub/sub vs queue |144| **Networking** | Front Door, Application Gateway, Load Balancer, Traffic Manager | Global vs regional, L4 vs L7, WAF |145| **AI services** | Azure OpenAI, AI Search, AI Foundry, Document Intelligence | Model needs, data grounding, orchestration |146| **Containers** | Container Apps, AKS, Container Instances | Operational control vs simplicity |147148---149150## Well-Architected Framework (WAF) Pillars151152| Pillar | Focus | Key Questions |153|--------|-------|---------------|154| **Reliability** | Resiliency, availability, disaster recovery | What is the RTO/RPO? How does it handle failures? Is there redundancy? |155| **Security** | Threat protection, identity, data protection | Is identity managed? Is data encrypted? Are there network controls? |156| **Cost Optimization** | Cost management, efficiency, right-sizing | Is compute right-sized? Are there reserved instances? Is there waste? |157| **Operational Excellence** | Monitoring, deployment, automation | Is deployment automated? Is there observability? Are there runbooks? |158| **Performance Efficiency** | Scaling, load testing, performance targets | Can it scale horizontally? Are there performance baselines? Is caching used? |159160### WAF Tradeoff Matrix161162| Optimizing for... | May impact... |163|-------------------|---------------|164| Reliability (redundancy) | Cost (more resources) |165| Security (isolation) | Performance (added latency) |166| Cost (consolidation) | Reliability (shared failure domains) |167| Performance (caching) | Cost (cache infrastructure), Reliability (stale data) |168169---170171## Performance Antipatterns172173| Antipattern | Problem | Fix |174|-------------|---------|-----|175| **Busy Database** | Offloading too much processing to the database | Move logic to application tier, use caching |176| **Busy Front End** | Resource-intensive work on frontend request threads | Offload to background workers/queues |177| **Chatty I/O** | Many small I/O requests instead of fewer large ones | Batch requests, use bulk APIs, buffer writes |178| **Extraneous Fetching** | Retrieving more data than needed | Project only required fields, paginate, filter server-side |179| **Improper Instantiation** | Recreating expensive objects per request | Use singletons, connection pooling, HttpClientFactory |180| **Monolithic Persistence** | Single data store for all data types | Polyglot persistence — right store for each workload |181| **No Caching** | Repeatedly fetching unchanged data | Cache-aside pattern, CDN, output caching, Redis |182| **Noisy Neighbor** | One tenant consuming all shared resources | Bulkhead isolation, per-tenant quotas, throttling |183| **Retry Storm** | Aggressive retries overwhelming a recovering service | Exponential backoff + jitter, circuit breaker, retry budgets |184| **Synchronous I/O** | Blocking threads on I/O operations | Async/await, non-blocking I/O, reactive streams |185186---187188## Mission-Critical Design (99.99%+ SLO)189190| Design Area | Key Considerations |191|-------------|-------------------|192| **Application platform** | Multi-region active-active, availability zones, Container Apps or AKS with zone redundancy |193| **Application design** | Stateless services, idempotent operations, graceful degradation, bulkhead isolation |194| **Networking** | Azure Front Door (global LB), DDoS Protection, private endpoints, redundant connectivity |195| **Data platform** | Multi-region Cosmos DB, zone-redundant SQL, async replication, conflict resolution |196| **Deployment & testing** | Blue-green deployments, canary releases, chaos engineering, automated rollback |197| **Health modeling** | Composite health scores, dependency health tracking, automated remediation, SLI dashboards |198| **Security** | Zero-trust, managed identity everywhere, key rotation, WAF policies, threat modeling |199| **Operational procedures** | Automated runbooks, incident response playbooks, game days, postmortems |200201---202203## Architecture Review Workflow204205### Step 1: Identify Requirements206207```text208Functional: What must the system do?209Non-functional:210 - Availability target (e.g., 99.9%, 99.99%)211 - Latency requirements (p50, p95, p99)212 - Throughput (requests/sec, messages/sec)213 - Data residency and compliance214 - Recovery targets (RTO, RPO)215 - Cost constraints216```217218### Step 2: Select Architecture Style219220Match requirements to architecture style using the selection criteria table above.221222### Step 3: Choose Technology Stack223224Use the technology choices decision framework. Prefer managed services (PaaS) over IaaS.225226### Step 4: Apply Design Patterns227228Select relevant patterns from the 44 cloud design patterns based on identified concerns.229230### Step 5: Address Cross-Cutting Concerns231232- **Identity & access** — Microsoft Entra ID, managed identity, RBAC233- **Monitoring** — Application Insights, Azure Monitor, Log Analytics234- **Security** — Network segmentation, encryption at rest/in transit, Key Vault235- **CI/CD** — GitHub Actions, Azure DevOps Pipelines, infrastructure as code236237### Step 6: Validate Against WAF Pillars238239Review each pillar systematically. Document tradeoffs explicitly.240241### Step 7: Document Decisions242243Use Architecture Decision Records (ADRs):244245```markdown246# ADR-NNN: [Decision Title]247248## Status: [Proposed | Accepted | Deprecated]249250## Context251[What is the issue we're addressing?]252253## Decision254[What did we decide and why?]255256## Consequences257[What are the positive and negative impacts?]258```259260---261262## Related Skills263264This skill complements:265- **azure-architecture-patterns** — Detailed Azure-specific patterns266- **bicep-avm-mastery** — Infrastructure as code for Azure267- **security-review** — STRIDE, threat modeling268- **observability-monitoring** — Production visibility269270---271272## References273274- [Azure Architecture Center](https://learn.microsoft.com/en-us/azure/architecture/)275- [Well-Architected Framework](https://learn.microsoft.com/en-us/azure/well-architected/)276- [Cloud Design Patterns](https://learn.microsoft.com/en-us/azure/architecture/patterns/)277- [Mission-Critical Workloads](https://learn.microsoft.com/en-us/azure/architecture/framework/mission-critical/)