Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 268 discussion

Rds proxy is for too many connections, not for performance

RDX proxy will :"improve the user experience while minimizing changes".

users are experiencing long delays. This is the priority issue , so we need to use cache service urgently to solve this issues. If we need performence , we can use proxy. But in this case , latency is our priority. So Answer is A.

A: Correct. Not suitable for write-heavy applications though. B: Reduces pressure on the database by reusing connections, but cannot address the slow-read problem. C: Why? Who would do this? D: It completely changes the architecture.

Use Amazon ElastiCache in front of the database.

A. Use Amazon ElastiCache in front of the database. Explanation: Amazon ElastiCache is a managed caching service that can be placed in front of the database to cache frequently accessed data. By caching the most common queries, it can significantly reduce the load on the database, leading to faster response times and an improved user experience. This solution minimizes changes to the existing architecture because it doesn't require modifications to the application's core logic or database schema. Instead, it optimizes performance by reducing the need for repetitive database reads. ElastiCache supports both Redis and Memcached, which are widely used for caching in web applications.

A for sure

answer should be B

Not B because this can help with connection management and improve scalability and availability but won't directly address read performance issues caused by high read traffic.

Another vague question from AWS: I would prefer A over B

A Caching frequently accessed data: ElastiCache can be used to reduce the load on your database by caching frequently accessed data. This can improve application performance and reduce the number of read queries to your database. Real-time applications: If your application requires real-time data processing, ElastiCache can help. Since it provides sub-millisecond response times, it can be used to power applications like gaming leaderboards, chat applications, and real-time analytics.

ask is - minimum changes. RDS Proxy is a feature of Amazon RDS. This would be easiest option to try.

Elasticache - reduce load due to read operations RDS proxy - reduce load due to lot of connections Here problem is read operations thus A is solution

I vote for Elasticache

B - "Use RDS Proxy between the application and the database." B because it improves the user experience while minimizing the changes. If A is used, you have to modify your application to get the data from the cache first, if it is not there, then get from db; and also to invalidate the cache if there is a db update.

https://docs.aws.amazon.com/AmazonElastiCache/latest/APIReference/Welcome.html

RDS Proxy: It helps applications improve scalability and performance by managing database connections and pooling, which can significantly reduce the load on the database. By using RDS Proxy, you can offload connection management tasks from your application and optimize database access, thereby improving read performance without making significant changes to the application's architecture. Minimizing Changes: Implementing RDS Proxy does not require architectural changes to the application. It works as a proxy layer between the application and the RDS database, so the application code remains unchanged. This minimizes the effort and risk associated with making modifications to the application.