Overall Satisfaction with Amazon Relational Database Service
At my current organization, we are using Amazon Relational Databases as our first option databases, supporting our DevOps environment. Currently, our monitoring system (based on Zabbix) and our configuration management system (based on Puppet) are using it as the main database. In our team, all databases are being based on AWS RDS PostgreSQL so far.
- AWS products on average, excel at high availability. RDS is a good example of that.
- Easy scaling. Just a few clicks.
- Load balancing in a transparent way.
- Sometimes you can't install specific items like modules.
- You are not able to use different DB versions from those provided by AWS.
- AWS keeps DB logs for a short time. If you have a problem and need to check something beyond the retention period, you can't.
- You can easily increase your database environment without a huge investment.
- If you need specific resources that are not available without huge customization, maybe RDS is not the best approach for you.
- AWS also provides its DB flavour, called Aurora, which intends to be faster, reliable and cheaper than traditional commercial solutions like MS SQL Server and Oracle.
Actually you can have most of these tools through AWS Relational Database Service as they are basically those technologies provided as a service. It is way better to have those products provided as a service through a huge and reliable infrastructure like AWS.