skills.rest
memasanz
memasanzCOMMUNITY
Explore all skills by this author →
GitHub

cloud-solution-architect

Designs and reviews Azure cloud architectures using Well-Architected Framework principles and design patterns.

1|Updated May 29, 2026
Search Tags:#system design#design patterns#microservices#azure#architecture review#cloud architecture#well-architected framework
One-click install
npx skills add https://github.com/memasanz/agent-harness --skill cloud-solution-architect-memasanz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloud-solution-architect
Source: https://github.com/memasanz/agent-harness/tree/main/.github/skills/cloud-solution-architect
Command: npx skills add https://github.com/memasanz/agent-harness --skill cloud-solution-architect-memasanz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing production-grade cloud systems requires navigating hundreds of Azure services, architecture styles, and design patterns. This Skill guides systematic architecture decisions so designs meet reliability, security, cost, and performance targets without missing critical tradeoffs. ## Core Features & Use Cases - Architecture Style Selection: Compares N-tier, Web-Queue-Worker, microservices, event-driven, big data, and big compute styles with selection criteria. - 44 Cloud Design Patterns: Maps patterns like Circuit Breaker, CQRS, Saga, and Bulkhead to Well-Architected Framework pillars. - Technology Decision Frameworks: Provides selection guidance for compute, storage, data, messaging, networking, and AI services on Azure. - Structured Review Workflow: Walks through requirement identification, style selection, pattern application, WAF validation, and ADR documentation. - Use Case: When asked to design a multi-tenant SaaS backend on Azure, the Skill helps select a microservices style, choose AKS and Cosmos DB, apply sharding and deployment stamps patterns, and validate the design against all five WAF pillars. ## Quick Start Ask the agent to design an Azure architecture for your workload, for example: design a highly available event-driven order processing system on Azure with a 99.99% availability target.

Frequently Asked Questions about cloud-solution-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose an Azure architecture style for my application?▼

Match your requirements to one of six styles: N-tier for traditional enterprise apps, Web-Queue-Worker for background processing, microservices for complex domains with independent teams, event-driven for real-time systems, and big data or big compute for analytics and HPC workloads.

How do I select between Azure compute services like AKS, Container Apps, and Functions?▼

Evaluate hosting model, scaling needs, cost, and team skills. Use Functions for event-driven tasks, Container Apps for simplified container hosting, AKS when you need full Kubernetes control, and App Service for traditional web apps.

What is the Azure Well-Architected Framework review process?▼

The review evaluates a design against five pillars: Reliability, Security, Cost Optimization, Operational Excellence, and Performance Efficiency. Each decision is checked against pillar-specific questions, and tradeoffs between pillars are documented explicitly.

Which cloud design patterns improve reliability in distributed systems?▼

Key reliability patterns include Circuit Breaker to stop calling failing services, Retry with exponential backoff for transient faults, Bulkhead to isolate failures, Saga for distributed transactions, and Health Endpoint Monitoring for automated failover.

What performance antipatterns should I avoid in Azure applications?▼

Common antipatterns include chatty I/O, no caching, synchronous I/O, retry storms, noisy neighbors, and monolithic persistence. Fixes involve batching requests, cache-aside patterns, async operations, circuit breakers, and polyglot persistence.

When should I use microservices instead of an N-tier architecture?▼

Choose microservices when the domain is complex, teams need independent deployment and scaling, and frequent updates are required. N-tier fits simpler domains, single teams, and lift-and-shift migrations where layered separation is sufficient.

Related Skills

Explore More Software Engineering Skills→
LazyIsEfficientLazyIsEfficient
15

system-architect

Frame scalable architectural designs with service boundaries and non-functional requirements for RFCs.

Official
Advanced
webrix-aiwebrix-ai
1

sprint-planning

Analyze sprint capacity and prioritize Jira or Linear backlog items.

Official
Intermediate
EanLeeEanLee

senior-security

Automate threat modeling, security audits, and penetration testing.

Community
Advanced
wesleyegbertowesleyegberto
3

multi-cloud-architecture

Plan multi-cloud architectures across AWS, Azure, and GCP with a decision framework.

Community
Advanced