Files
Jonathan Boniface bc84ee4df6
Some checks failed
check agents / check (push) Failing after 13s
Solution architecture outcome pattern: agent and its MCP servers
The cp1-solution-architecture-agent and the sa-aws/azure/gcp-cloud MCP servers, a separate
stream from the individual and sub-agent patterns.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 22:13:25 +00:00

4.9 KiB

name, metadata, description
name metadata description
azure-waf-performance-efficiency
category
WellArchitectedFramework
Generates performance efficiency guidance for Azure workloads based on the Performance Efficiency pillar of the Azure Well-Architected Framework. Use when setting performance targets, planning capacity, selecting service tiers, or designing scaling, partitioning and performance testing on Azure.

Azure Well-Architected Framework skill for the Performance Efficiency pillar

Overview

The Performance Efficiency pillar keeps every interaction efficient as demand grows. Every system has a limit beyond which it needs redesign or human work, so targets, capacity and scale units are decided in the design and tested in a production-like environment.

Core principles

The recommendations below follow the published framework. Written for this agent from Microsoft's published design review checklist. Codes are Microsoft's.

Relevant products

The following are examples of products relevant to this pillar:

  • Scaling: Autoscale, Virtual Machine Scale Sets, AKS cluster autoscaler, KEDA
  • Delivery: Azure Front Door, Azure CDN
  • Data: Azure Managed Redis, Cosmos DB partitioning, Azure SQL read replicas
  • Testing: Azure Load Testing, Application Insights

Workload assessment questions

Ask appropriate questions to understand the requirements and constraints of the workload and the organization. Choose from this list:

  • What are the numeric targets for latency, throughput and concurrency?
  • What is the expected peak, and when does it happen?
  • What is the workload's scale unit?
  • Which flows matter most under load?
  • Where is data read and written, and at what rate?
  • Where are users, relative to the workload's regions?
  • How is performance tested before release?

Validation checklist

Use this checklist to evaluate the architecture against this pillar:

  • Each critical flow has a numeric target.
  • Capacity is planned against a stated peak, and quotas are checked.
  • Service tiers are justified against the targets.
  • Scaling is automatic, with limits set.
  • Data partitioning and caching match the access pattern.
  • Performance baselines are recorded and compared.
  • Load tests run in a production-like environment.
  • Routine operations are scheduled away from peak.