AWS RDS a good use case
January 16, 2024
AWS RDS a good use case
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Amazon Relational Database Service (RDS)
We started using RDS as an alternative to our BE system since, at the beginning, the team did not have experience or knowledge about BE frameworks, but it was necessary to maintain a relationship between the data of the projects being executed and the RDS services of Amazon were of great help, since it is an out of the box solution. As well as it also served as a starting point to understand how our BE system should be structured later.
- Easy to implement
- Lots of documentation and tutorials available, from Amazon and third parties
- Low cost
- The official documentation needs to be sharped.
- Tools to move data from one server to another
- Easy to monitor the resources been consumed and the cost of it
- Higher availability
- No need to invest in additional hardware
- AWS Auto Scaling and Amazon Elastic Kubernetes Service (EKS)
The AWS relational database service was selected because at the early stages of the implementation of the company product the team didn't have a lot of experience in creating and configuring database inside the company cluster, but there was a need to have a relation database, and since other services from amazon where already been used, it sound wise to explore the RDS.
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