Amazon Relational Database Service (RDS) vs. Redis Enterprise Cloud™*

When we need to store the data that is structured and we know the format of the new entries then it is best to use Amazon RDS as a cloud service. It may not be well suited when the data is not structured and the new entries may have a different format.

Incentivized

Redis Cloud is very well suited for scenarios where fast data access is required or somewhat unstructured data needs to be stored. For us, it has worked very well for user session storage. However, if you have large amounts of structured data that is not frequently accessed, Redis is not the solution and a traditional relational database is likely more appropriate.

Incentivized

• Automated Database Management: We use it for streamlining routine tasks like software patching and database backups.
• Scalability on Demand: we use it to handle traffic spikes, scaling both vertically and horizontally.
• Database Engine Compatibility: It works amazingly with multiple database engines used by different departments within our organization including MySQL, PostgreSQL, SQL Server, and Oracle.
• Monitoring: It covers our extensive monitoring and logging, and also has great compatibility with Amazon CloudWatch

Incentivized

• Ease of setup and deployment via Heroku
• Reliability and splicity
• Fair pricing

Incentivized

• The whole snapshot backup & restore feature could be more informative to let users know clearly that restoring a snapshot means creating a whole new cluster
• As usual, AWS documentations need time to get used to
• Pricing & scaling could be more transparent

Incentivized

• The only area of improvement I have found is the documentation is sometimes lacking and could be a little more comprehensive.

Incentivized

We do renew our use of Amazon Relational Database Service. We don't have any problems faced with RDS in place. RDS has taken away lot of overhead of hosting database, managing the database and keeping a team just to manage database. Even the backup, security and recovery another overhead that has been taken away by RDS. So, we will keep on using RDS.

Incentivized

I've been using AWS Relational Database Services in several projects in different environments and from the AWS products, maybe this one together to EC2 are my favourite. They deliver what they promise. Reliable, fast, easy and with a fair price (in comparison to commercial products which have obscure license agreements).

Incentivized

We had contacted the AWS technical support request handling team and was a good experience with them. It is very simple to raise a concern request stating your concerns and they are there to help you overcome it within few hours and 1-2 days. Additionally they also provide service/support plan options that can be of help.

Incentivized

the online training & digital content available on the web from AWS was having sufficient information to deploy and run the service

Incentivized

Running MySQL RDS was a simpler solution than running standalone MySQL servers as the semi-managed nature of RDS saved us the need to install, maintain, secure, and backup our database servers. Using MySQL RDS was in addition to running MongoDB Atlas workloads and allowed us to use both relational and non-relational databases as needed

Incentivized

I've used Heroku Redis and RedisToGo. Redis Cloud has the best free/developer plan, and we have never had an issue.

Incentivized

• Increased costs due to having to have a consultant to manage security and more advanced features of AWS and RDS.
• The cost of the volume and storage of bds is very competitive with the previous services used.
• Its purported Amazon RDS customers can lower their total database operating costs by an average of 40% over three years, achieving a 264% return on investment.

Incentivized

• Redis Cloud is very affordable and therefore the cost is negligible when compared to the benefits— immediate ROI with very little startup costs.

Incentivized