A company is migrating an on-premises database to Amazon RDS for MySQL. The company has read-heavy workloads. The company wants to refactor the code to achieve optimum read performance for queries.
Which solution will meet this requirement with LEAST current and future effort?
To achieve optimum read performance for queries in a read-heavy workload, deploying Amazon RDS with one or more read replicas is the most effective solution. Read replicas allow the distribution of read traffic, significantly enhancing read performance while offloading the primary database. Modifying the application code to direct read queries to the read replicas ensures that the workload is efficiently balanced, minimizing future maintenance efforts and optimizing performance.
Multi-AZ is for disaster recovery, not read scalability or performance.
Read heavy access need read replicas as the right solution.
C answer
It's C.
Read Replicas for high performance read operations
Keyword: heavy read
C it is as it clearly mentions they want to achieve optimum read performance
C answer
Keyword: Achieve Optimum read performance for queries. Answer: Use Read Replicas and use that specific URL for read queries.
easiest solution is to use multi-az rds deployment with 2 readable standby instances setting up read replica is more effort than checking a single option
ni mada ra
C. El uso de replicas de lectura, aliviana las consultas intensivas sobre la BD principal
C... No Question
C forever
Option A and B are both talking about Multi AZ RDS instance which gives Primary and Secondary(Non Read Replica). This is good for high availability but will not help in reads. Read replica or Multi AZ Cluster deployment is the only option to achieve high reads.
C is the correct answer.
Option C is wrong because deploying a read replica will be more effort then just enabling the multi-AZ with RDS and also the multi-AZ is meant for high availability that's why option B is correct.
Option C provides the most straightforward and effective solution for improving read performance with minimal changes to the current application code and the least ongoing maintenance effort. Deploying read replicas allows for scaling read capacity and distributing read traffic efficiently.