Reliability, Cost, and Architecture Judgment
The question for this group
Can this system survive a failure, and is its complexity worth the cost?
Bring the earlier groups together; advance by explaining trade-offs and testing recovery.
Topics to explore
- Failure boundaries: single points of failure, Availability Zones, health checks, failover, and capacity limits.
- Recovery: backups versus availability, restore drills, RPO, RTO, and disaster recovery choices.
- Load behavior: load testing, autoscaling lag, rate limiting, caching, and graceful degradation.
- Cost and security review: idle resources, data transfer, NAT, logs, storage lifecycle, WAF, and access review.
- Architecture decisions: Well-Architected review, managed-service trade-offs, and documenting why a design fits.
- Advanced awareness: Organizations, multi-account governance, multi-Region systems, Kubernetes/EKS, and platform engineering.
Practice target
Review your deployed project, run one recovery drill, estimate its ongoing cost, and explain which advanced components it does not yet need.