Item: Amazon Relational Database Service (RDS)
Rating: 9
Author: Mayank Bansal

Use Cases and Deployment Scope

Currently, we are using a lot of backend application that needs a database. RDS is easy to configure and easy to manage compared to traditional on-prem databases where you need a dedicated DBA team, but here we are able to manage it. We were facing latency issues earlier due to cloud to on-prem latency, but everything is smooth.

Pros and Cons

Automatic backup.
Easy to configure and manage.
HA with Multi-AZ setup in nominal cost and effort.

Table defragmentation happens, and the process degrades. There should be a mechanism for defragmenting.

Return on Investment

Cost is reduced.
Fewer resources to manage the database.
Better functionality leads to higher output.

Alternatives Considered

Azure SQL Managed Instance and Oracle Autonomous Database

I have used other cloud providers databases too but RDS provides various flavors that other cloud providers do not provide. It also provides better network security compared to other PaaS database solutions provides.

Key Insights

Do you think Amazon Relational Database Service (RDS) delivers good value for the price?

Yes

Are you happy with Amazon Relational Database Service (RDS)'s feature set?

Yes

Did Amazon Relational Database Service (RDS) live up to sales and marketing promises?

Yes

Did implementation of Amazon Relational Database Service (RDS) go as expected?

Yes

Would you buy Amazon Relational Database Service (RDS) again?

Yes

Likelihood to Recommend

It is best suited when you are hosting applications too on cloud so it becomes easy to connect and you can have internal communication on your VPC. RDS also provides you the option to explore various different DB like Aurora, MySQL, and Oracle.

Explosive feature and RDX(S).

Overall Satisfaction with Amazon Relational Database Service (RDS)