A company has a mobile game that reads most of its metadata from an Amazon RDS DB instance. As the game increased in popularity, developers noticed slowdowns related to the game's metadata load times. Performance metrics indicate that simply scaling the database will not help. A solutions architect must explore all options that include capabilities for snapshots, replication, and sub-millisecond response times.
What should the solutions architect recommend to solve these issues?
To address the issue of slow metadata load times from the Amazon RDS DB instance while providing capabilities for snapshots, replication, and sub-millisecond response times, the best option is to add an Amazon ElastiCache for Redis layer in front of the database. Redis supports advanced features such as snapshots for persistence and replication for high availability and scalability. It also offers sub-millisecond response times, which are crucial for high-performance applications like mobile games. These capabilities make Redis a suitable choice for enhancing the performance of the game's metadata handling.
Option C is better as we need replication and snapshots
C is correct as only Redis support snapshot feature :https://aws.amazon.com/elasticache/redis-vs-memcached/
Thinking the capabilities with "snapshots, replication, and sub-millisecond response times" is for the Database or selected solution(ElastiCache).
C is correct
C is correct
Réponse C
:https://aws.amazon.com/elasticache/redis-vs-memcached/
Option D