A gaming company hosts a multiplayer game that uses an Amazon RDS for PostgreSQL DB instance to store player profiles. During peak hours, the game servers perform a high volume of read-only queries to retrieve player stats, causing the DB instance's CPU utilization to reach 100% and impacting gameplay. A solutions architect must scale the database to resolve the CPU bottleneck. Which database configuration should the solutions architect implement?
- ADeploy Amazon ElastiCache for Memcached with multi-AZ replication enabled and route read queries through the cache.
- BEnable RDS Multi-AZ deployment and configure the game servers to route read-only queries to the secondary standby DB instance.
- Create Amazon RDS Read Replicas and update the game server configuration to direct read-only queries to the replica endpoints.Answer
- DConfigure the database's Auto Scaling group with a very short cooldown period to launch new database instances immediately during peak traffic.
Answer
Create Amazon RDS Read Replicas and update the game server configuration to direct read-only queries to the replica endpoints.
Creating Amazon RDS Read Replicas is the correct solution because it scales database read capacity horizontally. By routing read-only queries to the replica endpoints, the game servers offload query processing from the primary DB instance, reducing its CPU usage. The replication is asynchronous, which is suitable for player profile reads that can tolerate slight replication lag.
Step-by-Step Solution
Key Concept
Read scaling in Amazon RDS using Read Replicas versus passive high-availability standbys in Multi-AZ deployments.