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

Microsoft Azure Cosmos DB vs SingleStore comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Apr 6, 2025

Review summaries and opinions

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

Categories and Ranking

Microsoft Azure Cosmos DB
Ranking in Database as a Service (DBaaS)
6th
Ranking in Vector Databases
1st
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
93
Ranking in other categories
NoSQL Databases (5th), Managed NoSQL Databases (1st)
SingleStore
Ranking in Database as a Service (DBaaS)
11th
Ranking in Vector Databases
15th
Average Rating
8.8
Reviews Sentiment
7.4
Number of Reviews
6
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2025, in the Database as a Service (DBaaS) category, the mindshare of Microsoft Azure Cosmos DB is 2.0%. The mindshare of SingleStore is 1.8%, up from 0.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Database as a Service (DBaaS)
 

Featured Reviews

MichaelJohn - PeerSpot reviewer
Very efficient for application-facing scenarios
There are several areas for improvement. Firstly, having a local development emulator or simulator for Azure Cosmos DB would be beneficial. It would be very handy to have a Docker container that developers can use locally. Although, I know there is a free tier and so on and so forth, having a local environment would be nice. For example, SQL Server is very portable. You can even install it on your machine. That is the number one thing that is missing in Azure Cosmos DB. The second improvement area is the IDE of choice. That means how you interact with Azure Cosmos DB. For example, with SQL Server, you have SQL Server Management Studio. I know there is a little bit of support for Azure Cosmos DB in Azure Data Studio, but it is not heavily advertised or it does not feel like first-class citizen support. Developer experience or developer tooling is missing in terms of interacting with the database. Better developer tools or an IDE for interacting with Azure Cosmos DB would enhance the developer experience. Lastly, there is some mixed messaging about what Azure Cosmos DB is, given its multiple APIs. There are so many Azure Cosmos DB APIs available. There is NoSQL. There are MongoDB, Gremlin, and others. There is still some mixed messaging for others who are new to Azure Cosmos DB about what Azure Cosmos DB is. Is this like MongoDB, but then there is also MongoDB in Azure Cosmos DB? I know it well, and I know that the default one is just NoSQL, but others I have interacted with over the last ten years or so get confused.
Yasin Sarı - PeerSpot reviewer
High-speed data processing, seamless scalability, and excellent high availability making it an optimal choice for those prioritizing performance and efficiency in a database solution
There's a noteworthy consideration when it comes to collecting massive amounts of data. It is not the optimal choice for direct data collection through queries, and it's more suited for aggregation tasks. Attempting to use it for direct extraction, for instance, might lead to memory-related challenges. While MySQL version five might lack extensive SQL capabilities, SingleStore also has its constraints, requiring simpler SQL writing. This becomes evident when seeking advanced functionalities like window functions or JSON functions, where SingleStore doesn't offer an extensive toolkit, necessitating a more straightforward approach to SQL.

Quotes from Members

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

Pros

"Microsoft Azure Cosmos DB offers exceptional stability, boasting a reliability rating of 99.95 percent."
"The high speed of Azure Cosmos DB compared to other competitors is remarkable."
"The solution is used because we get faster response times with large data sets than with SQL."
"Microsoft Azure Cosmos DB offers the response times needed for advanced analytics applications."
"The availability and latency of Azure Cosmos DB are excellent."
"Cosmos is preferred because of its speed, robustness, and utilization. We have all the merchandising information in Cosmos DB, which provides concrete and optimized data when searching for new products on the site. It is faster than other relational databases."
"The most valuable feature of the solution is that it is scalable with multiple master files."
"The features most valuable to us in Microsoft Azure Cosmos DB are the auto scale and change feed. These features allow us to do some operations that are not possible with SQL Server."
"The ability to store data in memory is a standout feature, enhanced by robust failover mechanisms."
"The product can automatically reinstall and reconfigure in case of a shutdown."
"The paramount advantage is the exceptional speed."
"It's a distributed relational database, so it does not have a single server, it has multiple servers. Its architecture itself is fast because it has multiple nodes to distribute the workload and process large amounts of data."
"The most valuable feature is the ability to create pipelines, streamline and extract data from the pipelines."
"MemSQL supports the MySQL protocol, and many functions are similar, so the learning curve is very short."
 

Cons

"We should have more freedom to tweak it and make our own queries for non-traditional use-cases."
"Overall, it works very well and fits the purpose regardless of the target application. However, by default, there is a threshold to accommodate bulk or large requests."
"Microsoft Azure Cosmos DB's performance could be better. In large volumes of documents, the querying process becomes slow and complicated."
"From about half a billion rows, we're returning maybe 20,000 in two or three minutes. We don't know why, but we are working with Microsoft and a third party to figure that out."
"In that scenario, two things can be improved."
"The current data analytics of Cosmos DB is inefficient for large-scale queries due to its transactional design."
"It's still new, and good training resources are harder to find. Even the most recent books on Cosmos DB are several years old, which is ancient in IT terms."
"Cosmos DB is expensive, and the RU-based pricing model is confusing."
"It is not the optimal choice for direct data collection through queries, and it's more suited for aggregation tasks."
"Poor key distribution can significantly impact performance, requiring a backward approach in design rather than adding tables incrementally."
"We don't get good discounts in Pakistan."
"There should be more pipelines available because I think that if MemSQL can connect to other services, that would be great."
"Having the ability to migrate servers using a single command would be extremely beneficial."
"For new customers, it's very tough to start. Their documentation isn't organized, and there's no online training available. SingleStore is working on it, but that's a major drawback."
 

Pricing and Cost Advice

"Its price is very good for the basic stuff. When you go to a more complicated use case, especially when you need replication and availability zones, it gets a little costly."
"Its pricing is not bad. It is good."
"Most customers like the flexibility of the pricing model, and it has not been an issue. They can start small, and the cost grows with adoption, allowing efficient management of the budget. Its pricing model has not been a concern at all for any of our customers. They understand it. It is simple enough to understand. Oftentimes, it is hard to forecast the RUs, but, in general, it has been fine."
"Cosmos DB is a PaaS, so there are no upfront costs for infrastructure. There are only subscriptions you pay for Azure and things like that. But it's a PaaS, so it's a subscription service. The license isn't perpetual, and the cost might seem expensive on its face, but you have to look at the upkeep for infrastructure and what you're saving."
"The pricing and licensing model was initially difficult to understand, but as soon as I learned what was going on and how it was priced, it was pretty easy."
"It is cost-effective. They offer two pricing models. One is the serverless model and the other one is the vCore model that allows provisioning the resources as necessary. For our pilot projects, we can utilize the serverless model, monitor the usage, and adjust resources as needed."
"This cost model is beneficial because it allows for cost control by limiting resource units (RUs), which is ideal. However, for our needs, we can't engage with their minimum pricing, which ranges from 100 to 1,000 RUs. At the bare minimum, we need to use 4,000 RUs for a customer. I would like to find a way to gain some advantages from the lowest tier, particularly the ability to scale down if necessary. It would be helpful to have more flexibility in cost management at the lower end."
"The solution is a bit on the expensive side."
"SingleStore is a bit expensive."
"The product's licensing is not expensive. It is comparable."
"I would advise users to try the free 128GB version."
"They have two main options: cloud installation and bare-metal installation, each with different pricing models."
"Using it for analytical purposes can be cost-effective in the long run, especially in terms of infrastructure."
report
Use our free recommendation engine to learn which Database as a Service (DBaaS) solutions are best for your needs.
857,688 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Legal Firm
14%
Comms Service Provider
10%
Computer Software Company
10%
Financial Services Firm
10%
Financial Services Firm
34%
Computer Software Company
12%
University
5%
Retailer
5%
 

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?
We are not consuming so much yet since we are at the beginning of using this solution. I would rate the pricing of Microsoft Azure Cosmos DB a six out of ten.
What needs improvement with Microsoft Azure Cosmos DB?
We are at the beginning of production, and everything is working very well. The price can always be lower, but currently, it's not a problem.
What do you like most about SingleStore DB?
The paramount advantage is the exceptional speed.
What is your experience regarding pricing and costs for SingleStore DB?
Using it for analytical purposes can be cost-effective in the long run, especially in terms of infrastructure. While building an on-premise cluster incurs an initial cost for servers with ample RAM...
What needs improvement with SingleStore DB?
There's a noteworthy consideration when it comes to collecting massive amounts of data. It is not the optimal choice for direct data collection through queries, and it's more suited for aggregation...
 

Also Known As

Microsoft Azure DocumentDB, MS Azure Cosmos DB
No data available
 

Overview

 

Sample Customers

TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
400+ customers including: 6sense, Adobe, Akamai, Ant Money, Arcules, CARFAX, Cigna, Cisco, Comcast, DELL, DBS Bank, Dentsu, DirectlyApply, EY, Factors.AI, Fathom Analytics, FirstEnergy, GE, Goldman Sachs, Heap, Hulu, IMAX, impact.com, Kroger, LG, LiveRamp, Lumana, Nvidia, OpenDialog, Outreach, Palo Alto Networks, PicPay, RBC, Samsung, SegMetrics, Siemens, SiteImprove, SiriusXM, SK Telecom, SKAI, SONY, STC, SunRun, TATA, Thorn, ZoomInfo.
Find out what your peers are saying about Microsoft Azure Cosmos DB vs. SingleStore and other solutions. Updated: May 2025.
857,688 professionals have used our research since 2012.