An online transaction processing (OLTP) system for financial ledger tracking requires a database strategy that achieves read latencies under 10 milliseconds and a near-zero Recovery Point Objective (RPO). The database workload is read-heavy with unpredictable traffic spikes. Which database architecture satisfies these criteria while dynamically scaling read capacity?
- ADeploy an Amazon RDS for MySQL database in a Multi-AZ deployment, and configure the client applications to direct read queries to the standby replica in the secondary Availability Zone during traffic spikes.
- Deploy an Amazon Aurora MySQL DB cluster with Aurora Auto Scaling configured for Aurora Replicas to dynamically scale read capacity based on CPU utilization.Cevap
- CDeploy a single-node Amazon RDS for MySQL database and configure an AWS Backup plan to restore the database to another Availability Zone with an RTO of 15 minutes when a failure occurs.
- DDeploy an Amazon Aurora MySQL DB cluster and configure cross-account replica scaling by using the default AWS-managed KMS key (aws/rds) to share the underlying database storage volume with standby reader instances in a separate AWS account.
Cevap
Deploy an Amazon Aurora MySQL DB cluster with Aurora Auto Scaling configured for Aurora Replicas to dynamically scale read capacity based on CPU utilization.
The correct architecture uses an Amazon Aurora cluster with Aurora Replicas and Aurora Auto Scaling. Aurora Replicas share the same underlying storage volume as the primary instance, meaning replication lag is minimal (usually under 100 milliseconds) and reads are served with sub-10ms latency. Aurora Auto Scaling can dynamically add replicas in response to spikes in CPU utilization or connections, ensuring read capacity scales horizontally.
Adım Adım Çözüm
Anahtar Kavram
Amazon Aurora replication and auto-scaling capabilities for read-heavy workloads