RDS database performance issue solution

[kung]

Scenario: “A leading blockchain company…cost-effective and suitable options to solve the database performance issue? (Choose 2)”

Correct marked answers: ‘Read Replica’ + ‘Provisioned IOPS’

Now I understood from earlier discussion that while improving RDS performance the way to go is always: Read Replica + Cache

So there is an answer option “Implement sharding to the RDS instances and set up database caching with Amazon ElastiCache Service.”

You mention sharding not entirely supported. I don’t read that out of this blogpost https://aws.amazon.com/blogs/database/sharding-with-amazon-relational-database-service/

So I would say this other option -besides ‘Read Replica’- of ‘sharding+elasticache’ is a valid option as well!

Cheers,
Robert

[TutorialsDojo-Support]

Hello Robert,

Thanks for the feedback.

The questions want you to choose “which of the following are the cost-effective”.

“Implement sharding to distribute the incoming load to multiple RDS MySQL instances.”

– Yes, this option increases read-performance as well as write performance too. You will have to set up multiple databases for sharding, so it would add complexity and not cost-effective, just to increase your read performance. You don’t want to pay for something you will not use.

Regards,

Kenneth Samonte @ Tutorials Dojo