RDS lives up to the ability for fast, secure, and configurable databases
Overall Satisfaction with Amazon Relational Database Service
RDS is being used in a ton of different ways, however it shines best for use in conjunction with Elasticsearch and providing the endpoint a writable position that we don't have to manage. Being multizone it allows for it to always be up and working; also since backups are automatic, it takes off that overhead of our engineering team.
Pros
- Automatic backups
- Multi-zone
- Completely managed service
Cons
- One thing I'd love to have is the ability to run actual SQL commands on it from the command line with typical SQL workbench type tools.
- Developers are releasing code quicker that rely on backend databases
- Backup and restore are handled by Amazon, meaning we know that our highly available database will always be available
- Ability to use multiple different databases depending on need
- Highly available configuration is included with just the click of a radio button with initial setup
We originally were going to utilize EC2 instances for configuration and installing a database. This would require DBA knowledge as well as the need for more overhead within our configuration. This could be scripted, however; this adds so much more to what our end goal was going to require. Within Terraform, this would require startup scripts and certificates, RDS handled all of this for us and made a much more easily configurable infrastructure as code.
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
Comments
Please log in to join the conversation