Azure Cosmos DB vs Redis

• Turn-key geo-redundancy with multi-master writes is unprecedented and unparalleled in the industry!
• Guaranteed low latency makes Cosmos DB an excellent fit for most of our performance-intensive situations.
• The tunable consistency model simplifies so many challenges in distributed systems engineering that otherwise require advanced knowledge of computer science topics. I continue to be impressed at how Cosmos DB has abstracted away so much complexity.

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

• Cosmos DB can be very expensive if you're using it for scenarios that are better completed in regular old Azure Table Storage or Blob Storage, specifically if you put some thought into your partitioning schemes. No product is a good substitute for thoughtful system design.
• It would be helpful if I had some more insight into how many resources (DTUs) an individual query uses.
• The auto-indexing is great, but a little mysterious -- not usually an issue but it does require some intentional thought.

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

• Tremendously reduced our time-to-market with solutions built on graph databases
• Helped our team to think more broadly about data by making NoSQL options much more accessible
• Saved us significant effort on geo-replication and global availability

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