We used to have a separate database. We managed everything, including scaling. We faced memory issues when there were too many hits, so we manually increased or cleaned the memory. Amazon RDS is automatically scalable. No intervention is needed. Upscaling and downscaling happen automatically.

Now, we have tighter controls. Earlier, we had roles mapped with AD integrations to the server where the database is. We used to do a lot of work. Now, we have IAM integration. If a person has a particular IAM role, they can access it. Amazon RDS has good authentication, operation, and autoscaling. It has features similar to an ordinary database. We get to do the same job without worrying about the infrastructure.

Less time was spent maintaining MySQL. Having to configure each server and spinning up a new MySQL in RDS takes 10 to 15min. It's a huge time-saving in maintenance. 

By using RDS, AWS takes care of the maintenance of the hardware and software updates. Being able to scale quickly or downsize with no impact is also great.

All of your databases are nicely organized under 1 interface; you have quick access to some monitors and Cloudwatch can be used to set up alerts based on thresholds and notify you. 

Today, with Terraform, you can automate the full process of creating RDS servers, deprecating them, changing their size, adding a replica, etc.

The product provides ease of management. We do not have to worry about the database. We just worry about the data. It is really convenient.

My company decided to use the solution since it is a managed database service that provides control along with a UI for our databases.

Amazon RDS has helped in reducing the median cost for on-prem services.

It takes off a load in setting up the VM, infrastructure, software and user accounts that go with databases.

The provisioning is much faster. You don't have to prepare hardware or install software. You just need to create an instance and you have a database.

We have some cases where our customers are looking for more performance or simplifying their DR. So, in this way, we have some cases where the customers moved from EC2 using enterprise license to Amazon RDS with less cost or with included standardization. So, we have cases of moving from EC2 to RDS to simplify the management and also simplify the DR strategy.

The solution has helped us have valuable metrics on our customer's business.

Currently, we are not using RDS as, it has some limitations on DB schema creation, it allows limited tenant DB creations...expecting to release RDS custom RDS very soon

It makes it easy to administer the database. It helps to scale your database by providing Read Replicas, which reduce transaction time. It is highly available and durable which helps in disaster recovery and management. 

It is also secure. You can build your own VPC and host the database inside it, which will produce robust security. You still need to follow the principles of security as highlighted by Amazon. 

Few minutes to launch RDS, DR, HA and monitoring configurations which reduced the administrative task and by the approach of pay for what we use reduced the cost. Performance is good when both Web application and DB are in same cloud. Need to be have In depth understanding of cost, else we are in position to pay more, which makes us to think our own DB is better when cost is very huge amount.  

For many of the Pythian customers, one salient benefit, among other benefits, is the option of spinning up a new instance whenever it is needed. Now it can be done with a few clicks, without much ado.

We are using it as shared QA environment.