Cloud Solution Architect

Cloud Solution Architect

Overview

Design well-architected, production-grade cloud systems following Azure Architecture Center best practices. This skill provides:

• 10 design principles for Azure applications
• 6 architecture styles with selection guidance
• 44 cloud design patterns mapped to WAF pillars
• Technology choice frameworks for compute, storage, data, messaging
• Performance antipatterns to avoid
• Architecture review workflow for systematic design validation

Ten Design Principles for Azure Applications

Architecture Styles

Selection Criteria

• Domain complexity → Microservices (high), N-tier (low-medium)
• Team autonomy → Microservices (independent teams), N-tier (single team)
• Data volume → Big data (TB+), others (GB)
• Latency requirements → Event-driven (real-time), Web-Queue-Worker (tolerant)

Cloud Design Patterns

44 patterns organized by primary concern. WAF pillar mapping: R=Reliability, S=Security, CO=Cost Optimization, OE=Operational Excellence, PE=Performance Efficiency.

Messaging & Communication

Reliability & Resilience

Data Management

Design & Structure

Security & Access

Deployment & Scaling

See Design Patterns Reference for detailed implementation guidance.

Technology Choices

Decision Framework

For each technology area, evaluate: requirements → constraints → tradeoffs → select.

See Technology Choices Reference for detailed decision trees.

Best Practices

See Best Practices Reference for implementation details.

Performance Antipatterns

Avoid these common patterns that degrade performance under load:

Mission-Critical Design

For workloads targeting 99.99%+ SLO, address these design areas:

See Mission-Critical Reference for detailed guidance.

Well-Architected Framework (WAF) Pillars

Every architecture decision should be evaluated against all five pillars:

WAF Tradeoff Matrix

Architecture Review Workflow

When reviewing or designing a system, follow this structured approach:

Step 1: Identify Requirements

Functional: What must the system do?Non-functional:  - Availability target (e.g., 99.9%, 99.99%)  - Latency requirements (p50, p95, p99)  - Throughput (requests/sec, messages/sec)  - Data residency and compliance  - Recovery targets (RTO, RPO)  - Cost constraints

Step 2: Select Architecture Style

Match requirements to architecture style using the selection criteria table above.

Step 3: Choose Technology Stack

Use the technology choices decision framework. Prefer managed services (PaaS) over IaaS.

Step 4: Apply Design Patterns

Select relevant patterns from the 44 cloud design patterns based on identified concerns.

Step 5: Address Cross-Cutting Concerns

• Identity & access — Microsoft Entra ID, managed identity, RBAC
• Monitoring — Application Insights, Azure Monitor, Log Analytics
• Security — Network segmentation, encryption at rest/in transit, Key Vault
• CI/CD — GitHub Actions, Azure DevOps Pipelines, infrastructure as code

Step 6: Validate Against WAF Pillars

Review each pillar systematically. Document tradeoffs explicitly.

Step 7: Document Decisions

Use Architecture Decision Records (ADRs):

# ADR-NNN: [Decision Title]
## Status: [Proposed | Accepted | Deprecated]
## Context[What is the issue we're addressing?]
## Decision[What did we decide and why?]
## Consequences[What are the positive and negative impacts?]

References

• Design Patterns Reference — Detailed pattern implementations
• Technology Choices Reference — Decision trees for Azure services
• Best Practices Reference — Implementation guidance
• Mission-Critical Reference — High-availability design

Source

Content derived from the Azure Architecture Center — Microsoft's official guidance for cloud solution architecture on Azure. Covers design principles, architecture styles, cloud design patterns, technology choices, best practices, performance antipatterns, mission-critical design, and the Well-Architected Framework.