Best for storing structured data
Overall Satisfaction with Amazon Relational Database Service (RDS)
We need to store the persistent data such as order information and other insurance related information in a database for which we use Amazon RDS.
Our business revolves around being able to store the order data and keep it in sync with the real time changes in order data and then finally get an outcome for that order. RDS has been a service of choice for us as it has high concurrency and low latency as well as disaster recovery built into it.
Our business revolves around being able to store the order data and keep it in sync with the real time changes in order data and then finally get an outcome for that order. RDS has been a service of choice for us as it has high concurrency and low latency as well as disaster recovery built into it.
Pros
- Securely storing the data with high concurrency
- Replication of the data to another Availability Zone for disaster recovery
- Taking backups and snapshots for data recovery
Cons
- It is a little difficult to configure and connect to an RDS instance. The integration with ECS can be made more seamless.
- Exploring features within RDS is not very easy and intuitive. Either a human friendly documentation should be added or the User Interface be made intuitive so that people can explore and find features on their own.
- There should be tools to analyze cost and minimize it according to the usage.
- Storing the data securely is imperative to our business to process the orders and Amazon RDS solves that problem and also provides resiliency and scalability as a cloud service.
- If we configure the disaster recovery with Amazon RDS and it reduces the possibility of a downtime even in the case of a disaster.
- It has increased the overall productivity of the engineers as they don't have to spend the time of Database management.
Amazon RDS is more resilient and accepted industry wide when compared to its peers. Also, as we have other services on AWS so it would be easier to integrate with other services like ECS if we go with Amazon RDS. Furthermore, it would be more cost effective if we go with Amazon RDS and in particular Amazon RDS Aurora Engine for PostgreSQL.
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
Comments
Please log in to join the conversation