Skip to main content

How will you mitigate read-intensive database workloads?

Suppose you have a database and it has got a products table. And, there are 100 users. 60 users are reading data of product A and the remaining 40 users are reading data of product B.

You can do either one of the following:

1. You can create an elasticache cluster. Let the first among 60 users query product A and the remaining 59 users use the data from the cache. ElastiCache is effective in caching frequent requests.

2. Create read replicas to distribute the read-only traffic across multiple database instances this improving the read performance.

Comments

Popular posts from this blog

AWS Route53 - Private Hosted Zone

AWS - Error - An error occurred (ExpiredToken) when calling the DescribeStacks operation: The security token included in the request is expired

Error:   An error occurred (ExpiredToken) when calling the DescribeStacks operation: The security token included in the request is expired. Reason: It occurred when I ran a MAKE command with a profile having expired token (security credentials) Fix: Generate new security credentials (aws sts assume-role) and run the command again

AWS CloudTrail

AWS CloudTrail is an API monitoring service.  It records activities in your account. We can log those activities in S3 bucket It gives visibility to user activities e.g., if you want to know who created an EC2 instance, you can get the answer using CloudTrail Using CloudTrail, you can track changes to AWS resources in your accounts