A company runs a web application with a MySQL database hosted on Amazon RDS. The database is experiencing performance degradation due to a high volume of read and write requests for user session states. A solutions architect must improve database efficiency by moving the session state data to a dedicated caching layer. The caching solution must support multi-AZ replication to ensure session data is not lost if a primary cache node fails. Which caching and database optimization strategy should the solutions architect implement?
- AMigrate the session state data to an Amazon ElastiCache for Memcached cluster with automatic replication enabled.
- BEnable Multi-AZ deployment on the Amazon RDS MySQL database and configure the application to route read queries for session states to the standby replica.
- Migrate the session state data to an Amazon ElastiCache for Redis cluster with Multi-AZ replication enabled.Answer
- DSet up a cross-region Pilot Light database replication pattern using Amazon Aurora MySQL to synchronize the session data.
Answer
Migrate the session state data to an Amazon ElastiCache for Redis cluster with Multi-AZ replication enabled.
Migrating the session state data to an Amazon ElastiCache for Redis cluster with Multi-AZ replication enabled is the correct approach. Unlike Memcached, ElastiCache for Redis supports replication, Multi-AZ replication groups, and automatic failover, ensuring that session data remains available if a primary node fails.
Step-by-Step Solution
Key Concept
Selecting the appropriate caching engine (Redis vs. Memcached) based on replication and persistence requirements.
Estimated Time:1m 0s