Developer perspective of RDS.
September 19, 2023

Developer perspective of RDS.

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Amazon Relational Database Service (RDS)

We use RDS mainly for running managed database instances. We use MySql and PostgresSql mostly, with multi-az, monitoring, and replication features enabled. As for the scope and business problems, I don't think this is a product that solves any business problems directly; instead, it is used to support systems that actually solve them. Ans si does not have a specific scope except for providing persistence to backend systems.
  • Monitoring
  • Replication
  • Availability
  • Setup and Managing.
  • More Granular performance metric tracking is feasible.
  • Ability to restore backups across regions.
  • I don't have much idea on ROI for RDS as a product, but majorly we outsource Management of production DB instances since we don't have the right set of people to do so.

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?

I wasn't involved with the selection/purchase process

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

Yes

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

Yes

In most of the use cases where an RDBMS is required, RDS can easily be sufficient. It is easy to set up and manage. Works great specifically where there is no requirement for very granular control of the database, and does not have very high performace. Because RDS is not going to provide the level of granular control that you can have on self hosted DB as it is partially managed by AWS. And for high performance, RDS doesn't scale as good as products like Aurora. However, unless there are very specific requirements, RDS does the job most of the time.