Item: Amazon Relational Database Service (RDS)
Rating: 9
Author: Verified User

Overall Satisfaction with Amazon Relational Database Service (RDS)

Use Cases and Deployment Scope

At our organization, we use it for our revenue management and some publisher application database services. It is also a component of our performance goals and SLA improvements, and is tied to our CI/CD processes and is a foundation for expansion because of its ease of use, low learning curve to implement, and backup services it can link to.

Pros and Cons

Pros

Database backups and restoration processing
Security group management for access management
Blue green deployment features

Cons

Did not seem to allow for segmented RDS backup instances, you had to backup the full instance
Console commands and controls could be improved

Return on Investment

Supports business continuity planning and implementation in respect to replication and failover
Reduction in cost to run compared to competitors
Flexibility to work with many 3rd party technology solutions allows for faster prototyping and quicker time to market of products

Alternatives Considered

Azure Data Lake Storage

The main area that stuck out to me in looking at AWS RDS compared to Azure Data Lake Storage was still that RDS is simple to get up and running with over its competitors. The only negative and it holds true for both solutions is that can both be hard to estimate cost control at the beginning.

Key Insights

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

Other Software Used

Azure Data Lake Storage, Azure Bot Service (Microsoft Bot Framework), AWS Chatbot

Likelihood to Recommend

I honestly can't think of any use cases where it is not appropriate. The RDS service is well suited when tied to almost any 3rd party database engines. I say almost any because I have not used them all and tested! It is a very low cost to run solution, and even in scenarios where backups are considered. This is an important fact when coming to thinking about a full architecture plan. Great for situations in need of Scale, Failover, and Backup and Recovery.

Comments

Please log in to join the conversation

Simplified yet robust relational database service