Cloud Computing
Cloud Architecture Design
The AWS Well-Architected Framework defines five pillars: Operational Excellence, Security, Reliability, Performance Efficiency, and Cost Optimization. Senior cloud architects evaluate every design decision against these pillars simultaneously. The Well-Architected Tool runs automated checks against an account and produces a risk report - used in enterprise procurement, compliance audits, and architecture reviews.
- Slack's shared-nothing stateless compute layer handles 26M DAU - state is in databases and caches, compute scales horizontally by adding instances.
- GitHub's git hosting has a 4-hour RTO for full regional failover - the complexity of stateful git data replication determines the realistic recovery time.
- Figma uses persistent WebSocket servers for real-time collaboration and serverless Lambda for document processing - the right compute model per workload type.
Scalable Design
**Scalable Design** is a foundational pattern in Cloud Architecture Design. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Scalable Design is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
What is the primary operational benefit of Scalable Design?
Multi-Region Active-Active
**Multi-Region Active-Active** is a foundational pattern in Cloud Architecture Design. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Multi-Region Active-Active is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
What is the primary operational benefit of Multi-Region Active-Active?
Disaster Recovery Tiers
**Disaster Recovery Tiers** is a foundational pattern in Cloud Architecture Design. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Disaster Recovery Tiers is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
What is the primary operational benefit of Disaster Recovery Tiers?
Cost-Efficient Architecture
**Cost-Efficient Architecture** is a foundational pattern in Cloud Architecture Design. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Cost-Efficient Architecture is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
Cloud Architecture Design is primarily a theoretical concern - real teams just use managed services and ignore architectural patterns
Managed services reduce operational burden but do not eliminate the need for sound architectural decisions about failure modes, scaling, and cost
Managed services handle undifferentiated heavy lifting (patching, backups, failover) but the choice between them, their configuration, and their integration patterns still require deep architectural understanding.
What is the primary operational benefit of Cost-Efficient Architecture?
Summary
- **Scalable design:** horizontal scaling, stateless compute, externalized state (RDS, ElastiCache, SQS) - scale by adding instances, not upgrading instance size
- **Multi-region:** active-active (both regions serve traffic, data synchronization required) or active-passive (standby for DR, simpler data model) - RPO determines which
- **Disaster recovery tiers:** active-active (RPO ~0, RTO ~0), warm standby (RPO minutes, RTO minutes), pilot light (RPO hours, RTO hours), backup-restore (RPO days, RTO days)
- **Cost-efficient design:** Spot for batch, Reserved/Savings Plans for steady-state, serverless for variable workloads - cost is a first-class architectural concern
Related Topics
These topics form the broader Cloud Architecture Design ecosystem:
- Multi-Cloud and Hybrid — Multi-region active-active shares patterns with multi-cloud - data synchronization and DNS routing are similar challenges
- Cost Optimization — Architectural decisions (serverless vs EC2, Spot eligibility) determine cost before any RI purchase is made
- Cloud in Interviews — Well-Architected Framework pillars structure the evaluation portion of cloud system design interview answers
Вопросы для размышления
- How does the architecture for Cloud Architecture Design change when scaling from 1,000 to 10 million users?
- What are the primary failure modes in a Cloud Architecture Design system, and what monitoring detects them before users are affected?
- What trade-offs would change the architectural decision for Cloud Architecture Design in a regulated industry with strict data residency requirements?