Optimizing MySQL Performance in Amazon RDS | Increase Read Activity Solution | AWS Certified Database - Specialty

Increase Read Performance in Amazon RDS with Multi-AZ Configuration | AWS Certified Database - Specialty

Question

An application uses Amazon RDS for MySQL deployed in Multi-AZ configuration as the backend database.Users have started raising complaints regarding the performance of the application.It has been identified that the performance issues are caused by increased read activity on the database.What is the most performance optimized resolution to this problem?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Answer: D.

Option A is incorrect because Multi-AZ standby instances can't be used for read queries.

Option B is incorrect because Read Replicas is not the most performant solution.Read replica performance is dependent on the instance size.Amazon ElastiCache offers a better read performance solution.

Option C is incorrect because Read Replicas is not the most performant solution.Read replica performance is dependent on the instance size.Amazon ElastiCache offers a better read performance solution.

Option D is incorrect because Amazon ElastiCache provides a sub-millisecond response for read queries.

Reference:

https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/elasticache-use-cases.html#elasticache-use-cases-data-store

The most performance optimized resolution to the problem of increased read activity on the Amazon RDS for MySQL deployed in Multi-AZ configuration would be to deploy an RDS Read Replica in the same AZ as the master DB instance.

Explanation:

  • Multi-AZ configuration of Amazon RDS ensures high availability and failover support in case of any issues with the primary database instance. In this configuration, a standby replica of the primary database is maintained in a different Availability Zone (AZ) which can take over in case of any issues with the primary database.
  • Deploying an RDS Read Replica in the same AZ as the master DB instance allows read traffic to be offloaded from the primary instance to the replica, which improves the performance of the application. The read replica can handle the read traffic while the primary instance can focus on write traffic, reducing contention and optimizing the overall performance.
  • Deploying an RDS Read Replica in a different AZ to the master DB instance can also help improve performance, but it may add additional latency due to network traffic between the two AZs.
  • Configuring the application to read from the Multi-AZ standby instance may not be optimal as the standby instance is meant for failover purposes and may not be optimized for read traffic. It may also result in additional network latency as the application would have to read data from a different AZ.
  • Deploying an Amazon ElastiCache cluster in front of the RDS DB instance may improve performance by offloading read traffic to the cache, but it would add additional complexity to the architecture and may not be the most optimized solution for this specific scenario.

In summary, deploying an RDS Read Replica in the same AZ as the master DB instance is the most performance optimized solution for the given scenario.