Try our new research platform with insights from 80,000+ expert users

Microsoft Azure Cosmos DB vs Redis comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 29, 2024
 

Categories and Ranking

Microsoft Azure Cosmos DB
Ranking in NoSQL Databases
3rd
Ranking in Vector Databases
5th
Average Rating
8.2
Reviews Sentiment
7.3
Number of Reviews
75
Ranking in other categories
Database as a Service (DBaaS) (6th), Managed NoSQL Databases (1st)
Redis
Ranking in NoSQL Databases
7th
Ranking in Vector Databases
4th
Average Rating
8.8
Number of Reviews
19
Ranking in other categories
In-Memory Data Store Services (1st)
 

Featured Reviews

Michael Calvin - PeerSpot reviewer
Easy to integrate, has a shallow learning curve, and scales dynamically
Azure Cosmos DB is quick to adopt with a shallow learning curve. The average user can be operational within hours or days, handling small to medium data volumes. However, optimizing for ultra-high throughput scenarios involves a steeper learning curve, requiring substantial knowledge to master Azure Cosmos DB. Nonetheless, most users can leverage it as their operational data store with minimal effort. Our platform boasts several extensive language model features, particularly around summarization capabilities. We use vector searching in Azure Cosmos DB to facilitate the retrieval of an augmented generation model with our LLM implementation. It's a standard RAG implementation using Azure Cosmos DB. Compared to other options, a key advantage of vector indexing in Azure Cosmos DB is the ability to query documents alongside vectors. This pinpoints the precise information required for RAG in our LLM solution, granting us greater flexibility than vector searching in other Azure services. We integrated the vector database with the Azure OpenAI service for our LLM solution. The Azure AI services were simple to integrate with the vector database. There was a slight learning curve, especially as we were on the private preview of vector searching. This led to some hiccups with our existing database configurations, specifically regarding continuous backup. We couldn't enable continuous backup and vector searching simultaneously. However, this was solely due to our participation in the preview, and I'm confident this issue won't persist in the general availability release. Azure Cosmos DB is fantastic for searching large amounts of data when the data is within a single partition. Over the last two weekends, we ingested over 400 gigabytes of data into our Azure Cosmos DB database and saw no change in querying performance compared to when our database was only 20 gigabytes in size. This is impressive and powerful, but the scope is limited to those partition queries. The first benefit we've seen is increased developer productivity. Azure Cosmos DB is an easy database to work with. Its schema-less nature allows us to iterate quickly on our platform, develop new features, and store the associated data in Azure. Developers find it easy to use, eliminating the need for object-relational mapping tools and other overhead. Geographic replication and the ability to scale geographically is another advantage. This is challenging with other databases, even other NoSQL databases, but Azure Cosmos DB makes it easy. Cost optimization is a major benefit as well. We've been able to run our platform at a fraction of the infrastructure cost our customers incur when integrating with us. This allows us to focus resources on feature development and platform building rather than infrastructure maintenance. Azure Cosmos DB helped reduce the total cost of ownership. We don't need DBAs, system administrators, or typical IT staff to run the infrastructure because we can use Azure Cosmos DB as a platform or a software-as-a-service data storage solution. This makes the total cost of ownership significantly lower than any comparable solution using relational databases or other NoSQL solutions like MongoDB. We enable auto-scaling on all of our Azure Cosmos DB resources, which helps us achieve cost optimizations.
Yaseer Arafat - PeerSpot reviewer
Unmatched Performance and Scalability for Modern Applications
Redis has room for improvement in a few areas. Enhanced tools for managing and monitoring clusters would be beneficial, as would built-in security mechanisms like advanced encryption and granular access controls. Simplifying setup and configuration could make Redis more accessible to new users. Introducing more enterprise-grade features, such as better multi-tenancy support and improved backup and restore capabilities, would also be advantageous. For the next release, it would be great to see enhanced cluster management tools, native multi-region supports for better data redundancy, integrated analytics for deeper insights, AI and ML integration features, and improved developer experience through enhanced SDKs and tools.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Cosmos DB makes life easier because if we want to use Mongo-type data, or Cassandra-type data, or maybe even just a simple cable storage-type data, then graph, there are multiple ways to do this."
"As a NoSQL database, it offers schema flexibility which simplifies design and reduces initial engineering overhead."
"Cosmos DB's greatest strengths are its easy setup and affordability, especially for those who understand its usage."
"The connectors, such as the MongoDB connector and the integration with SQL, are incredibly valuable."
"We primarily use Cosmos DB because it's a managed platform service, eliminating concerns about hosting and reliability."
"Cosmos DB is effective at handling large queries."
"The customer gave us the feedback that they are able to easily find the data they are looking for. It is very quick."
"Cosmos DB performs exceptionally well and has not caused any issues that necessitate adjustments in nodes for improved performance."
"It is particularly efficient for cloud-based storage and operations."
"The best thing about Redis is its ability to handle large amounts of data without frequently hitting the database. You can store data in temporary memory, especially for high-volume data."
"I find Redis valuable primarily for its caching capabilities, particularly in handling cache requests effectively. Its simplicity in managing key-value pairs for caching is one of its strengths, making it a preferred choice over more complex databases like MongoDB for specific use cases. However, I haven't explored Redis extensively for managing complex data structures beyond caching, as MongoDB might be more suitable for such scenarios."
"Redis is a simple, powerful, and fast solution."
"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."
"The product offers fast access to my database."
"The solution is fast, provides good performance, and is not too expensive."
"It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology."
 

Cons

"Its stability can be further improved."
"There are multiple approaches to implementing multitenant architecture on Azure Cosmos DB, but there is still no single or best-recommended approach when you have a big variance in the size of your tenants. That is something that still needs to be worked on."
"If we have a lot of data, doing a real-time vector search is a performance challenge because the search happens over a large dataset. It consumes more time."
"The auto-scaling feature adjusts hourly. We have many processes that write stuff in batches, so we must ensure that the load is spread evenly throughout the hour. It would be much easier if it were done by the minute. I'm looking forward to the vector database search that they are adding. It's a pretty cool new feature."
"It would be beneficial if Cosmos supported batch and real-time use cases to make the system more seamless."
"A further simple application is required for Brazil."
"In the long run, there should be an addition of more features, especially because this space is evolving quickly. It all boils down to how many more features you are adding, how many integrations you are supporting, and how many more APIs you have that are standard APIs."
"In that scenario, two things can be improved."
"There is a lack of documentation on the scalability of the solution."
"It's actually quite expensive."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient."
"The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly."
"If we use a lot of data, it will eventually cost us a lot."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"The solution's pricing for a local installation is very expensive."
 

Pricing and Cost Advice

"Pricing, at times, is not super clear because they use the request unit (RU) model. To manage not just Azure Cosmos DB but what you are receiving for the dollars paid is not easy. It is very abstract. They could do a better job of connecting Azure Cosmos DB with the value or some variation of that."
"For the cloud, we don't pay for the license, but for the on-prem versions, we do pay."
"The RU's use case determines our license fees."
"It is expensive. The moment you have high availability options and they are mixed with the type of multitenant architecture you use, the pricing is on the higher end."
"Microsoft Azure Cosmos DB's licensing costs are monthly."
"Cosmos DB is expensive, and the RU-based pricing model is confusing. Although they have a serverless layer, there are deficiencies in what I can define and assign to a database. Estimating infrastructure needs is not straightforward, making it challenging to manage costs."
"From a startup point of view, it appears to be expensive. If I were to create my startup, it would not have the pricing appeal compared to the competition, such as Supabase. All those other databases are well-advertised by communities. I know there is a free tier with Azure Cosmos DB. It is just not well advertised."
"The price of Microsoft Azure Cosmos DB could be a bit lower."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is an open-source product."
"Redis is not an overpriced solution."
"The tool is open-source. There are no additional costs."
"Redis is an open-source solution. There are not any hidden fees."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
823,875 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Comms Service Provider
12%
Financial Services Firm
11%
Retailer
6%
Financial Services Firm
21%
Computer Software Company
15%
Educational Organization
7%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Microsoft Azure Cosmos DB?
The initial setup is simple and straightforward. You can set up a Cosmos DB in a day, even configuring things like availability zones around the world.
What is your experience regarding pricing and costs for Microsoft Azure Cosmos DB?
The solution was a new product, so we didn't have a cost of ownership before. The cost has not surprised us. It's not been an issue. If we were doing multi-master replication globally, the cost wou...
What needs improvement with Microsoft Azure Cosmos DB?
Using it is easy. We are having trouble optimizing it. I'm not a technical person, so I couldn't explain why, but we're not getting the performance we were expecting. I'm sure it's probably an us p...
What do you like most about Redis?
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you u...
What needs improvement with Redis?
Redis has room for improvement in a few areas. Enhanced tools for managing and monitoring clusters would be beneficial, as would built-in security mechanisms like advanced encryption and granular a...
What is your primary use case for Redis?
My primary use case for Redis is to enhance the performance of our web applications by using it as a caching layer. By caching frequently accessed data, we reduce the load on our primary databases,...
 

Comparisons

 

Also Known As

Microsoft Azure DocumentDB, MS Azure Cosmos DB
Redis Enterprise
 

Overview

 

Sample Customers

TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
1. Twitter 2. GitHub 3. StackOverflow 4. Pinterest 5. Snapchat 6. Craigslist 7. Digg 8. Weibo 9. Airbnb 10. Uber 11. Slack 12. Trello 13. Shopify 14. Coursera 15. Medium 16. Twitch 17. Foursquare 18. Meetup 19. Kickstarter 20. Docker 21. Heroku 22. Bitbucket 23. Groupon 24. Flipboard 25. SoundCloud 26. BuzzFeed 27. Disqus 28. The New York Times 29. Walmart 30. Nike 31. Sony 32. Philips
Find out what your peers are saying about Microsoft Azure Cosmos DB vs. Redis and other solutions. Updated: November 2024.
823,875 professionals have used our research since 2012.