The six pillars
diagram
Questions I ask in a review
- Reliability: what's the blast radius if one AZ fails? When did we last test a restore?
- Security: who can read tenant data, and how would we know if they did?
- Performance: which component saturates first at 10× load?
- Cost: what's the cost per tenant or per request, and does it fall as we grow?
- Ops: can a new engineer deploy safely on day one?
Note
Studying toward AWS Solutions Architect – Associate (SAA-C03), with GCP Professional Cloud Architect next. This page grows as I go.
Cheatsheet
The whole topic on one page. Click to open full screen.
Sources & further learning
Videos, courses, docs and books I recommend for this topic.
AWS Well-Architected FrameworkDocs · AWS · docs.aws.amazon.comAWS Skill Builder (free digital training)Course · AWS · skillbuilder.awsAWS Certified Solutions Architect – Associate (exam page)Course · AWS · aws.amazon.comAmazon Builders' LibraryArticle · AWS · aws.amazon.comAWS Well-Architected pillars — video searchVideo · YouTube · youtube.com
Related topics
System DesignUnderstood
How to Approach Any System Design
A repeatable framework — requirements, estimates, API, data model, high-level design, deep dives, trade-offs — plus the numbers every architect should know.
Foundation7 sources
Cloud & DeliveryUnderstood
Observability — Logs, Metrics, Traces
Know what your system is doing in production — the three pillars, OpenTelemetry, SLIs/SLOs, and alerting on symptoms not causes.
Intermediate4 sources
Architecture PatternsApplied in production
Multi-Tenant SaaS Architecture
Serve many customers from shared infrastructure while guaranteeing isolation of data, performance and configuration per tenant.
Advanced4 sources