Architecture learning guide
Start with the result users need. Compare normal and failure conditions with matching evidence before choosing a design. Begin with availability versus performance.
✓ 1 lesson available
Reason about availability and performance from requirements
Do not infer “available” or “fast” from instance counts or service names. Define successful use, then interpret fictional report results that pass normal operation only, a failure only, both conditions or remain unchecked.
- Define the required work, demand, acceptable wait and failure.
- Match results to those conditions and distinguish pass, fail and not checked.
- Identify further checks for redundancy, capacity changes and request distribution.
The prerequisite is Regions, AZs and failure boundaries. Completing all networking or database lessons is unnecessary; an AWS AZ provides the concrete example. AWS Regions vs Availability Zones: placement and failure boundaries →
Study availability versus performance →After the foundations, choose a design question
These are optional next readings. Check their prerequisites and choose the one that matches your question.
- After EC2 basics: capacity maintenance and scaling. EC2 Auto Scaling basics: minimum, desired and maximum capacity explained →
- After HTTP and networking: request distribution. What is ELB? ALB vs NLB, listeners, targets and health checks →
- After database and RDS basics: failure preparedness and read distribution. RDS Multi-AZ vs read replicas: availability, reads and failover →
Further architecture topics
Lessons on hybrid systems and migration are being prepared. Their guide URLs exist, but do not indicate completed lessons or a validated production design.