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

Google Cloud Spanner vs Microsoft Azure Cosmos DB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jul 13, 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

Google Cloud Spanner
Ranking in Database as a Service (DBaaS)
9th
Average Rating
9.0
Reviews Sentiment
7.8
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Microsoft Azure Cosmos DB
Ranking in Database as a Service (DBaaS)
6th
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
102
Ranking in other categories
NoSQL Databases (3rd), Managed NoSQL Databases (1st), Vector Databases (1st)
 

Mindshare comparison

As of August 2025, in the Database as a Service (DBaaS) category, the mindshare of Google Cloud Spanner is 5.1%, up from 3.5% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 2.8%, up from 0.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Database as a Service (DBaaS)
 

Featured Reviews

Ethan Lo - PeerSpot reviewer
A stable and scalable relational database that ensures a return on investment for its users
The most valuable feature of the solution is its scalability. Scalability comes with two options, among which Google Cloud Spanner can scale horizontally, compared to other relational databases that scale vertically. You can change Google Cloud Spanner's resource configuration, which is done through processing units. Suppose you set up Google Cloud Spanner initially with a hundred processing units, and then you run out of resources since your database used too much CPU. In the aforementioned scenario, you can scale up or down and face no downtime in the production phase. The solution's features are important when running a company twenty-four hours, seven days a week.
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.

Quotes from Members

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

Pros

"We can scale the solution if we need to."
"It is a very scalable solution."
"Google Cloud Spanner is stable."
"The most valuable feature of the solution is its scalability. Scalability comes with two options, among which Google Cloud Spanner can scale horizontally, compared to other relational databases that scale vertically."
"The application deployment in the cloud is the best feature of the infrastructure."
"Microsoft Azure Cosmos DB helped improve our organization's search result quality significantly when we started using it about eight years ago."
"Some of the best features of Microsoft Azure Cosmos DB are that it could scale, and we could still use SQL language."
"It is one of the simpler databases to work with in terms of code management, tracking, and debugging due to its straightforward data storage and retrieval mechanisms."
"Overall, I would rate Microsoft Azure Cosmos DB a nine out of ten."
"The connectors, such as the MongoDB connector and the integration with SQL, are incredibly valuable."
"The user interface of Microsoft Azure Cosmos DB is the best part of the entire Microsoft ecosystem; I find it to be the best user interface you can ever hope for, especially when compared to AWS and GCP, which do not measure up as well."
"Microsoft Azure Cosmos DB has reduced our total cost of ownership by about half, allowing us to sell our product for about half of what we were selling it before, and Microsoft Azure Cosmos DB is probably 70% of the reason why that's true."
"With Azure being our main cloud, the valuable features of Microsoft Azure Cosmos DB include integration with other Azure products that we're using and governance inside Azure. For integration with other products inside the Azure cloud, it was a better choice."
 

Cons

"Google came up with something called Cloud Spanner Emulator, which fails to work like the real product if I want to develop some code and run a database locally on my machine."
"The tool needs to improve horizontal scaling."
"The cost can be a bit high."
"I want to improve the deployment of cameras and surveillance infrastructure."
"The tool lacks to offer AI features."
"The integration with other solutions needs to improve because Cosmos DB's interoperability is lacking in some scenarios. For example, I'm currently implementing Fabric. That involves migrating from environments without apps, processing data and users, and taking them to Fabric."
"The query searching functionality has some complexities and could be more user-friendly. Improvements in this area would be very helpful."
"We had to go to forums to check if it was failing for everyone else. It was surprising that a large organization like Microsoft doesn't provide an official statement about the maintenance or issues that could impact our overall usage."
"There are some disadvantages as it is costly compared to other NoSQL databases."
"There are no specific areas I believe need improvement as I am happy with what I am getting currently. However, I am open to new features in future versions, like possibly integrating AI features natively into Cosmos DB. Any improvement would be beneficial."
"The model with autoscaling for RU is complicated to optimize RU consumption."
"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."
"The main area of improvement is the cost, as the expense is high. Also, when writing processes into Cosmos, sometimes the threshold is met, which can be a problem if developers have not written the code properly, limiting calls to five thousand."
 

Pricing and Cost Advice

"It is expensive."
"Google Cloud Spanner is an expensive solution."
"The solution is expensive."
"Price-wise, I heard that Google Cloud Spanner is on the higher side."
"I would rate Cosmos DB's cost at seven out of ten, with ten being the highest."
"Pricing is one of the solution's main features because it is based on usage, scales automatically, and is not too costly."
"The customer had a high budget, but it turned out to be a little bit cheaper than what they expected. I am not sure how much they have spent so far, but they are satisfied with the pricing."
"Microsoft Azure Cosmos DB is moderately priced, where it is neither expensive nor cheap."
"For the cloud, we don't pay for the license, but for the on-prem versions, we do pay."
"When we've budgeted for our resources, it's one of the more expensive ones, but it's still not very expensive per month."
"Microsoft Azure Cosmos DB pricing is based on RUs. Reading 1 KB document costs one RU, whereas writing one document costs five RUs. Pricing for querying depends on the complexity of the query. If you increase the document size, it will automatically increase the RU cost."
"Cosmos DB gave us three accounts for $400. We pay according to the usage."
report
Use our free recommendation engine to learn which Database as a Service (DBaaS) solutions are best for your needs.
865,140 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Computer Software Company
12%
Manufacturing Company
9%
Retailer
8%
Legal Firm
13%
Financial Services Firm
11%
Comms Service Provider
10%
Computer Software Company
10%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your primary use case for Google Cloud Spanner?
Google Cloud Spanner has all the features of a traditional relational database, including schemas, SQL queries, ACID transactions, and provides excellent integration and monitoring tools as well as...
What is your experience regarding pricing and costs for Google Cloud Spanner?
Price-wise, I heard that Google Cloud Spanner is on the higher side. I am not sure if this is a rumor or if it's fake news, but I believe that having BigQuery and GCP together could be a little cos...
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 pricing for Microsoft Azure Cosmos DB is good, but there is a developer factor to consider. It could be economical or expensive depending on usage. Guidance about query consumption of Request U...
What needs improvement with Microsoft Azure Cosmos DB?
The only area Microsoft Azure Cosmos DB can improve on is its documentation; while it is solid and very useful, enhancements in the indexing documentation would help users save costs and make it mo...
 

Also Known As

Google Spanner
Microsoft Azure DocumentDB, MS Azure Cosmos DB
 

Overview

 

Sample Customers

Streak, Optiva, Mixpanel
TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
Find out what your peers are saying about Google Cloud Spanner vs. Microsoft Azure Cosmos DB and other solutions. Updated: July 2025.
865,140 professionals have used our research since 2012.