Home › Forums › AWS › AWS Certified Solutions Architect Professional › Wording in scenario confusing (dynamodb/sqs/high number of write operations) › Reply To: Wording in scenario confusing (dynamodb/sqs/high number of write operations)
MemberMay 31, 2020 at 3:15 pm
Thanks for sharing your feedback.
The question did not specifically say it is using EC2 instances with Apache/Nginx as the front-end for the incoming requests. It could be a separate setup, either a static page on S3 or another cluster of EC2 instances.
Either way, the question would like to find the best solution to scale and accommodate the incoming request to write to the database (in the order of millions).
“These features of the donation website will eventually result in a high number of write operations on their database tier considering that there are millions of generous donors around the globe who want to help. “
Yes, DynamoDB can scale and CloudFront can cache user requests, but DynamoDB has a limit for its scaling. SQS on the other hand can be store virtually an unlimited number of messages. So millions of requests can be temporarily stored while the consumer EC2 instances process each request and save it into the DynamoDB table. This reduces overhead for scaling IOPS for your DynamodDB, which is also expensive.
Kenneth Samonte @ Tutorials Dojo