Design and Deploy a Multi-Region Cloud Architecture
12 weeks · 0 milestones
Design a multi-region, active-active or active-passive architecture for a real or realistic system — deployed in at least two regions on a real cloud provider — with a written architecture document that includes: failure domain analysis (what breaks when Region A loses its primary database), stated RPO and RTO targets with justification, and cost-vs-resilience trade-off analysis explaining every architectural decision in terms of the specific failure scenario it addresses. The deployment must be live and accessible to the reviewer during review. Proof: a senior cloud architect or SRE asks 'what happens to your users in Region A if Region B loses its primary database right now?' — you must walk through your actual architecture's failure behaviour, not a hypothetical response.
Milestone map
Milestone map
3 milestones
Study the CAP theorem, PACELC theorem, and consistency models (eventual consistency, strong consistency, read-your-own-writes). Design a multi-region architecture for a write-heavy application: specify the data replication strategy (active-active vs active-passive), the consistency model for each data type, and the conflict resolution approach. Document the design in an Architecture Decision Record.
Proof required
Submit: an architecture design document (at least 600 words) for the multi-region data architecture including: replication topology diagram, consistency model per data type with justification, conflict resolution approach with an example of a conflict and how it would be resolved, and an ADR for the most significant architectural decision. A senior cloud architect or distributed systems engineer must review and confirm the design is coherent and the consistency model choices are justified.
What gets checked
- Design specifies consistency models per data type — not a single consistency model for the entire system
- Conflict resolution approach includes a concrete example showing how a specific conflict would be resolved
- A senior cloud architect or distributed systems engineer has confirmed the design is coherent