Item: Amazon Relational Database Service (RDS)
Rating: 9
Author: Verified User

Use Cases and Deployment Scope

We mainly use AWS in our org and are transitioning everything to VPC. One of the use cases was to have an RDBMS that supports several databases such as MySQL, Postgres, and the likes. AMAZON RDS checked all the boxes and made it easier for us to manage everything on AWS.

Pros and Cons

Supports MySQL, PostgreSQL.
Useful if you want to leverage Aurora.
Highly scalable.
Supports dynamic scaling.

Scale down is a bit buggy.

Return on Investment

Decreased overall CapEx since we use AWS in our org.
Easier to maintain as we now have a single team that manages resources in AWS.

Alternatives Considered

Teradata Aster Database

We did a POC on Teradata Aster as well but Amazon RDS is miles ahead. Plus customer support is next level. AWS is easier to use and has CLI functionality that is constantly evolving.

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

Other Software Used

Amazon Aurora, Informatica Cloud MDM - Customer 360 for Salesforce, RStudio

Likelihood to Recommend

Easy to create and configure. Front-end configuration makes it easier for non DBAs to maintain and manage databases on Amazon RDS. Well integrated with AWS' fine-grained and role-based security. Highly scalable and supports dynamic scaling which takes away the overhead of constantly monitoring databases for space/memory issues.

If you don't need additional overhead, Amazon RDS is the way to go

Overall Satisfaction with Amazon Relational Database Service (RDS)