๐๏ธ Architecture & Well-Architected Framework
1
The AWS Well-Architected Framework
The AWS Well-Architected Framework provides a consistent approach for customers and partners to evaluate architectures, and implement designs that can scale over time.
The Six Pillars
- Operational Excellence โ ability to run and monitor systems to deliver business value. Key practices: Infrastructure as Code (CloudFormation), CI/CD pipelines, small reversible changes.
- Security โ protecting information and systems. Key practices: implement a strong identity foundation, enable traceability, apply security at all layers, automate security best practices, protect data in transit and at rest.
- Reliability โ ability to recover from failures and dynamically acquire resources. Key practices: test recovery procedures, automatically recover from failure, scale horizontally.
- Performance Efficiency โ using computing resources efficiently. Key practices: use serverless architectures, experiment more often, go global in minutes.
- Cost Optimisation โ avoiding unnecessary costs. Key practices: adopt a consumption model, measure overall efficiency, stop spending on undifferentiated heavy lifting.
- Sustainability โ minimising environmental impacts. Key practices: understand your impact, maximise utilisation, use managed services.
2
High Availability & Fault Tolerance
High Availability (HA)
Systems designed to remain operational even if some components fail. AWS services that enable HA: Elastic Load Balancing (ELB), Auto Scaling Groups (ASG), Multi-AZ deployments (RDS, ElastiCache), Route 53 health checks and failover routing.
Fault Tolerance vs High Availability
- Fault Tolerant โ system continues to function even when components fail (zero downtime); requires redundancy at every layer.
- Highly Available โ system is designed to recover quickly from failure (minimal downtime); uses redundancy but may have brief outages during failover.
Disaster Recovery Strategies
- Backup & Restore โ cheapest; backup data to S3; longest RTO/RPO.
- Pilot Light โ minimal version of environment always running; scale up when needed.
- Warm Standby โ scaled-down but fully functional version always running.
- Multi-Site Active/Active โ most expensive; fastest recovery; run at full capacity in multiple regions simultaneously.