Soru

Zorluk: OrtaResilient Database Configurations and High Availability

A SaaS provider is migrating its core multi-tenant application to AWS and requires a PostgreSQL-compatible database. The database architecture must guarantee high availability within a single AWS Region, with a Recovery Time Objective (RTO) of less than 30 seconds and a Recovery Point Objective (RPO) of near zero (under 1 second). Which database configuration meets these requirements with the lowest operational overhead?

  1. A
    Amazon RDS for PostgreSQL DB instance with one or more Read Replicas deployed in different Availability Zones, using a Route 53 latency routing policy to direct write traffic during a failover
  2. B
    A single-node Amazon RDS for PostgreSQL DB instance with automated daily snapshots copied to a standby pilot light EC2 instance hosting PostgreSQL in another Availability Zone
  3. Amazon Aurora PostgreSQL DB cluster with a Multi-AZ deployment containing a writer instance and a reader instance in a different Availability ZoneCevap
  4. D
    Amazon RDS for PostgreSQL DB instance deployed in a Multi-AZ DB instance configuration with a cross-Region Read Replica, using Route 53 Latency routing to automate cross-Region failover

Cevap

Amazon Aurora PostgreSQL DB cluster with a Multi-AZ deployment containing a writer instance and a reader instance in a different Availability Zone
The correct configuration is the Amazon Aurora PostgreSQL DB cluster with a Multi-AZ deployment. Amazon Aurora utilizes a shared storage volume replicated across three Availability Zones. If the primary instance fails, Aurora automatically promotes a reader instance (Aurora Replica) in another Availability Zone to primary. This failover process typically takes less than 30 seconds, satisfying the RTO. Because the storage volume is shared and updated synchronously, the RPO is near zero.

Adım Adım Çözüm

1
Analyze RTO and RPO constraints.
The architecture requires an RTO of less than 30 seconds and an RPO of under 1 second (near zero).
This eliminates slow recovery mechanisms (such as snapshot restoration) and asynchronous replication strategies that depend on manual failover.
2
Compare RDS Multi-AZ DB instance failover time with the requirements.
Standard RDS Multi-AZ DB instance failover takes 60 to 120 seconds because it requires database recovery on the standby instance.
This failover duration exceeds the 30-second RTO threshold, eliminating standard RDS Multi-AZ options.
3
Evaluate Amazon Aurora Multi-AZ failover and replication capabilities.
Amazon Aurora automatically promotes an Aurora Replica in another Availability Zone in less than 30 seconds. The shared storage design ensures near-zero RPO without data loss.
Aurora meets both strict RTO and RPO limits out of the box with minimal operational management.

Anahtar Kavram

Amazon Aurora Multi-AZ failover and shared storage architecture
Tahmini Süre:1m 30s
Bu soruyu puanla