Amazon RDS vs Redis

• For engineers with experience managing databases, setup is simple. And for the uninitiated, the RDS console interface becomes intuitive with some practice.
• Not having the maintain the underlying infrastructure is a great benefit of using RDS. Patching and backups can be scheduled from the console and from then on are pretty much automated.
• Right-sizing the DB instance to perform optimally with an application can be a very simple procedure. If a DB instance is not struggling to keep up, the instance size can be scaled up with just a few clicks.
• Baseline configurations are generally sane for most RDS instances. This allows novice developers and engineers to get the most out of the service without being a complete database administrator.

Read full review

• Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
• Reliable. With a proper multi-node configuration, it can handle failover instantly.
• Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
• Fast. We process tens of thousands of RPS and it doesn't skip a beat.

Read full review

• There should be a proper listing of all parameter groups alongside the instances that they are attached to. This would help to see which instances would be affected if a parameter group is changed.
• RDS should allow SUPER privilege to the master user. A few advanced tasks(like getting a physical backup using MySQL Enterprise Backup) fail because SUPER privilege is not available for the master user.
• A few parameters are not modifiable in the parameter groups and the access to the server filesystem is not given. This should not be the case because as an advanced user, you might want to understand things a little deeper.

Read full review

• We had some difficulty scaling Redis without it becoming prohibitively expensive.
• Redis has very simple search capabilities, which means its not suitable for all use cases.
• Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.

Read full review

• Switching back to RDS from Redshift has made my BI Dashboards much more performant (though again, we're not dealing with data in the magnitudes that justify the Redshift toolset).
• It has decreased our tech debt. Engineering has been much more straight forward.
• Our uptime has been improved by removing unnecessary data migration processes.

Read full review

• Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
• Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
• Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.

Read full review