A company runs a critical transactional application on an Amazon RDS for PostgreSQL Multi-AZ DB instance. The database is currently sized as a instance to handle a combination of transactional writes and a heavy volume of read-only business intelligence (BI) queries. The transactional write workload is steady and low, but the BI queries cause CPU utilization to spike to during business hours. The company wants to optimize costs while maintaining high availability.
Which database design is the most cost-effective solution?
- Create an Amazon RDS Read Replica to handle the BI queries, and downsize the primary Multi-AZ DB instance to a instance.Cevap
- BConfigure the application to route the BI queries to the Multi-AZ standby DB instance to utilize its idle capacity, and downsize the primary instance to a instance.
- CConvert the Multi-AZ deployment to a Single-AZ deployment, create a Read Replica to handle the BI queries, and configure the Read Replica as the primary disaster recovery failover target.
- DMigrate the database to Amazon DynamoDB using Provisioned Capacity mode to handle both transactional writes and BI queries at a lower cost.
Cevap
Create an Amazon RDS Read Replica to handle the BI queries, and downsize the primary Multi-AZ DB instance to a instance.
The correct option offloads the read-heavy business intelligence queries to an Amazon RDS Read Replica. Since the primary database only needs to handle the steady, low-volume write transactions, the primary Multi-AZ instance (and its standby) can be safely downsized from to , resulting in significant cost savings while maintaining high availability.
Adım Adım Çözüm
Anahtar Kavram
Separation of read and write workloads using RDS Read Replicas to optimize Multi-AZ compute costs.