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 Jan 25, 2026

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)
8th
Average Rating
9.2
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)
4th
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
109
Ranking in other categories
NoSQL Databases (2nd), Managed NoSQL Databases (1st), Vector Databases (1st)
 

Mindshare comparison

As of January 2026, in the Database as a Service (DBaaS) category, the mindshare of Google Cloud Spanner is 6.4%, up from 3.8% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 4.1%, up from 0.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Database as a Service (DBaaS) Market Share Distribution
ProductMarket Share (%)
Microsoft Azure Cosmos DB4.1%
Google Cloud Spanner6.4%
Other89.5%
Database as a Service (DBaaS)
 

Featured Reviews

LJ
System Architect at UST Global España
Offers good performance to users
The tool lacks to offer AI features. In the future, I would like the product to offer AI features to users. Nowadays, we are creating small acronyms for our SQL Server. We put some templates. If I just put your name and stop it, the entire cloud can be explored, but such features are not there in Google Cloud Spanner. As a layman rather than a developer, if I create a tool or a procedure. If I write a procedure and then when you describe a procedure, a dummy procedure will be written for you, and it will be available for you as a template in SQL Server, but such kind features are not there in Google Cloud Spanner.
reviewer2724105 - PeerSpot reviewer
Senior Director of Product Management at a tech vendor with 1,001-5,000 employees
Provides super sharp latency, excellent availability, and the ability to effectively manage costs across different tenants
For integrating Microsoft Azure Cosmos DB with other Azure products or other products, there are a couple of challenges with the current system. Right now, the vectors are stored as floating-point numbers within the NoSQL document, which makes them inefficiently large. This leads to increased storage space requirements, and searching through a vast number of documents in the vector database becomes quite costly in terms of RUs. While the integration works well, the expense associated with it is relatively high. I would really like to see a reduction in costs for their vector search, as it is currently on the expensive side. The areas for improvement in Microsoft Azure Cosmos DB are vector pricing and vector indexing patterns, which are unintuitive and not well described. I would also like to see the parameters of Fleet Spaces made more powerful, as currently, it's somewhat lightweight. I believe they've made those changes intentionally to better understand the cost model. However, we would like to take a more aggressive approach in using it. One of the most frustrating aspects of Microsoft Azure Cosmos DB right now is that you can only store one vector per document. Additionally, you must specify the configuration of that vector when you create an instance of Microsoft Azure Cosmos DB. Once the database is set up, you can't change the vector configuration, which is incredibly limiting for experimentation. You want the ability to try different settings and see how they perform, as there are numerous use cases for storing more than one vector in a document. While interoperability within the vector database is acceptable—for example, I can search for vectors—I still desire a richer set of configuration options.

Quotes from Members

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

Pros

"The application deployment in the cloud is the best feature of the infrastructure."
"It is a very scalable solution."
"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."
"We can scale the solution if we need to."
"Google Cloud Spanner is stable."
"Azure Cosmos DB's graph queries are its most valuable feature. Although I have not yet explored vector search, it's coming to Cosmos DB, and I plan to look into it. Having data in a flat file format in a document database speeds up processes, which is the primary purpose. Additionally, Cosmos DB's use of the Mongo platform makes it intuitive and cost-effective."
"The solution is highly scalable."
"Reading and inserting data into Microsoft Azure Cosmos DB is a very smooth process."
"I appreciate Microsoft Azure Cosmos DB's robust document management and consistent availability."
"Cosmos DB has helped our organization handle large amounts of data."
"Cosmos DB is a document database that stores data in JSON format for faster retrieval of unstructured data. I personally appreciate the speed, which is significantly better for unstructured data, especially since Cosmos DB had JSON as a data type early on."
"Cosmos DB is stable and easy to use."
"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."
 

Cons

"The tool needs to improve horizontal scaling."
"The tool lacks to offer AI features."
"I want to improve the deployment of cameras and surveillance infrastructure."
"The cost can be a bit high."
"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."
"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."
"A better description and more guidance would help because the first time I created it, I didn't understand that a container is similar to a table in SQL."
"There is room for improvement in Microsoft's maintenance aspect. For example, we had a major incident at the end of December where the entire South Central region was down for our application, causing many problems due to a lack of access to the database."
"I hope they improve the service. Before last year, improvements on Cosmos DB were very slow."
"The RUs still appear to be a black box for everyone. Even though they explain read and write RUs, it remains unclear for many users."
"It is not as easy to use as DynamoDB."
"While Microsoft Azure Cosmos DB is generally easy to use, it has some limitations."
 

Pricing and Cost Advice

"It is expensive."
"Price-wise, I heard that Google Cloud Spanner is on the higher side."
"Google Cloud Spanner is an expensive solution."
"The solution is expensive."
"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."
"Microsoft Azure Cosmos DB is moderately priced, where it is neither expensive nor cheap."
"I would rate Cosmos DB's cost at seven out of ten, with ten being the highest."
"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."
"Microsoft provides fair pricing."
"It's expensive. I would rate it a seven out of ten for pricing."
"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."
"Azure Cosmos DB is generally a costly resource compared to other Azure resources. It comes with a high cost. We have reserved one thousand RUs. Free usage is also limited."
report
Use our free recommendation engine to learn which Database as a Service (DBaaS) solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
13%
Healthcare Company
10%
Media Company
8%
Legal Firm
13%
Financial Services Firm
11%
Comms Service Provider
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business33
Midsize Enterprise21
Large Enterprise58
 

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 needs improvement with Google Cloud Spanner?
The tool lacks to offer AI features. In the future, I would like the product to offer AI features to users. Nowadays, we are creating small acronyms for our SQL Server. We put some templates. If I ...
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?
Microsoft Azure Cosmos DB's pricing model has aligned with my budget expectations because I can tune the RU as I need to, which helps a lot. Microsoft Azure Cosmos DB's dynamic auto-scale or server...
What needs improvement with Microsoft Azure Cosmos DB?
I have not utilized Microsoft Azure Cosmos DB multi-model support for handling diverse data types. I'm not in the position to decide if clients will use Microsoft Azure Cosmos DB or any other datab...
 

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: December 2025.
881,082 professionals have used our research since 2012.