Google Cloud Spanner vs Microsoft Azure Cosmos DB comparison

Google Cloud Spanner vs. Microsoft Azure Cosmos DB

Download the complete report

Helped 893,244 peers since 2012

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

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 May 2026, in the Database as a Service (DBaaS) category, the mindshare of Google Cloud Spanner is 7.9%, up from 4.5% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 4.8%, up from 1.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Database as a Service (DBaaS) Mindshare Distribution
Product	Mindshare (%)
Microsoft Azure Cosmos DB	4.8%
Google Cloud Spanner	7.9%
Other	87.3%

Database as a Service (DBaaS)

Featured Reviews

LijomonJose

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.

Read full review

reviewer2724105

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.

Read full review

Quotes from Members

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

Pros

"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."

"Google Cloud Spanner is stable."

"The solution is stable and reliable."

"We can scale the solution if we need to."

"The application deployment in the cloud is the best feature of the infrastructure."

"It is a very scalable solution."

"Cosmos DB is a pretty stable solution. I would rate it a ten out of ten."

"It is easy to use because you don't need to know much about Cosmos DB or have prior experience."

"I would rate it a ten out of ten for stability."

"Cosmos is a PaaS, so you don't need to worry about infrastructure and hosting."

"Microsoft Azure Cosmos DB is easy to use and implement for application programmers."

"The solution is easy to use, and it is also easy to integrate with several things for database use cases."

"The most valuable features include the global write capability, which allows customers to read and write across different regions simultaneously, enhancing performance and availability."

"The ability to scale automatically is very valuable. Additionally, multi-region support automatically synchronizing to a different region for multi-region applications is a cool feature. It's more of a lift with other databases to configure that extra region and set up replication, even if it's on the cloud. With Azure, it's just a button click. It's that simple."

More Microsoft Azure Cosmos DB pros

Cons

"The cost can be a bit high."

"I want to improve the deployment of cameras and surveillance infrastructure."

"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 cost can be a bit high."

"The tool needs to improve horizontal scaling."

"The tool lacks to offer AI features."

"One area for improvement is the ease of writing SQL queries and stored procedures in Microsoft Azure Cosmos DB. Writing an SQL query and a stored procedure on top of that is a little challenging."

"One area of improvement for Cosmos database is the auto-scaling of RUs during high loads. It would be beneficial if the database could automatically scale resources rather than requiring manual adjustments."

"Better documentation on how to integrate with other components would be helpful because I was struggling with this."

"The first one is the ability to assign role-based access control through the Azure portal for accounts to have contributor rights."

"Its stability can be further improved."

"The cost is a concern. Microsoft Azure Cosmos DB did not decrease our total cost of ownership. From the standpoint of the old way of doing DBA operations, it did, but our cloud cost increased significantly."

"To show this in real time, we need a live connection that automatically updates in response to new records being inserted. This automated updating feature is lacking in Microsoft Azure Cosmos DB compared to Databricks."

"In that scenario, two things can be improved."

More Microsoft Azure Cosmos DB cons

Pricing and Cost Advice

"Price-wise, I heard that Google Cloud Spanner is on the higher side."

"Google Cloud Spanner is an expensive solution."

"The solution is expensive."

"It is expensive."

"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."

"The cost is the biggest limitation of this solution."

"Microsoft Azure Cosmos DB's licensing costs are monthly."

"If you are a small organization or startup building from scratch without the Microsoft Startup Founder Club support, it could be expensive."

"Our experience with the pricing and setup cost is that it aligns with what we expect based on the pricing we see. However, I would absolutely like it to be less if possible."

"It's expensive. I would rate it a seven out of ten for pricing."

"Cosmos DB is cost-effective when starting but requires careful management."

"Its cost is transparent. Pricing depends on the transaction and data size, but overall, it is cheaper compared to hosting it on your corporate network due to other factors like power consumption."

More Microsoft Azure Cosmos DB pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Database as a Service (DBaaS) solutions are best for your needs.

See recommendations

893,244 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

24%

Healthcare Company

Computer Software Company

Media Company

Financial Services Firm

12%

Legal Firm

11%

Comms Service Provider

Manufacturing Company

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

No data available

By reviewers
Company Size	Count
Small Business	33
Midsize Enterprise	22
Large Enterprise	58

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?

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...

What is your primary use case for Microsoft Azure Cosmos DB?

We have a very large team of developers who develop a solution for our customers. In the part where they need some infrastructure on Microsoft Azure, we deploy entire environments of different type...

Oracle Database as a Service vs Google Cloud Spanner

Comparisons

Compared 19% of the time

Yugabyte Platform vs Google Cloud Spanner

Compared 14% of the time

MongoDB Atlas vs Google Cloud Spanner

Compared 12% of the time

Yugabyte Cloud vs Google Cloud Spanner

Compared 10% of the time

Microsoft Azure SQL Database vs Google Cloud Spanner

Compared 6% of the time

More Google Cloud Spanner Competitors

MongoDB Atlas vs Microsoft Azure Cosmos DB

Compared 6% of the time

PostgreSQL vs Microsoft Azure Cosmos DB

Compared 5% of the time

Amazon DynamoDB vs Microsoft Azure Cosmos DB

Compared 5% of the time

MongoDB Enterprise Advanced vs Microsoft Azure Cosmos DB

Compared 5% of the time

Neo4j AuraDB vs Microsoft Azure Cosmos DB

Compared 3% of the time

More Microsoft Azure Cosmos DB Competitors

Product Reports

Database as a Service (DBaaS)

Download Google Cloud Spanner product report

Microsoft Azure Cosmos DB

Download Microsoft Azure Cosmos DB product report

Also Known As

Google Spanner

Microsoft Azure DocumentDB, MS Azure Cosmos DB

Overview

Google Cloud Spanner is a fully managed, scalable, globally distributed, and strongly consistent database service. It offers traditional relational database semantics alongside non-traditional scale and availability.

Google Cloud Spanner is designed for applications that require high availability, strong consistency, and the ability to scale across regions without sacrificing performance. It supports SQL semantics and guarantees ACID transactions. With seamless horizontal scaling, it enables businesses to automatically expand their databases in response to load demands, maintaining performance and reliability. Built with advanced technology, it provides developers the ability to focus on building applications without worrying about infrastructure complexity.

What are the key features of Google Cloud Spanner?

Global scale: Allows horizontal scaling across regions with ease.
Strong consistency: Ensures all read and write operations are atomic, consistent, isolated, and durable.
SQL support: Provides ANSI SQL support, allowing easy integration with existing applications.
Automatic sharding: Manages data partitioning under the hood for optimal performance.
High availability: Delivers an SLA of 99.999% uptime, crucial for business-critical applications.

What benefits or ROI should users consider?

Reduced operational complexity: Minimizes database management tasks, allowing focus on application development.
Cost efficiency: Optimizes resource usage and minimizes unnecessary provisioning costs.
Scalability: Supports application growth without infrastructure reengineering.
Consistent performance: Maintains high performance under heavy and variable workloads.

Google Cloud Spanner's implementation in the finance sector facilitates real-time transaction processing and fraud detection systems. In retail, it handles large volumes of transactional data, supporting services like inventory management. Healthcare uses it for managing patient data across geographic locations, ensuring data consistency and accessibility.

Google

Microsoft Azure Cosmos DB offers scalable, geo-replicated, multi-model support with high performance and low latency. It provides seamless Microsoft service integration, benefiting those needing flexible NoSQL, real-time analytics, and automatic scaling for diverse data types and quick global access.

Azure Cosmos DB is designed to store, manage, and query large volumes of both unstructured and structured data. Its NoSQL capabilities and global distribution are leveraged by organizations to support activities like IoT data management, business intelligence, and backend databases for web and mobile applications. While its robust security measures and availability are strengths, there are areas for improvement such as query complexity, integration with services like Databricks and MongoDB, documentation clarity, and performance issues. Enhancements in real-time analytics, API compatibility, cross-container joins, and indexing capabilities are sought after. Cost management, optimization tools, and better support for local development also require attention, as do improvements in user interface and advanced AI integration.

What are the key features of Azure Cosmos DB?

Scalability: Effortlessly handles scaling for large workloads.
Geo-replication: Provides global data access with low latency.
Multi-model Support: Compatible with diverse data types.
NoSQL Flexibility: Offers a non-relational database experience.
Real-time Analytics: Facilitates data-driven decision-making.
Automation: Simplifies scaling and maintenance processes.

What benefits can users expect from Cosmos DB?

High Performance: Ensures rapid processing and low latency.
Ease of Use: Features a user-friendly interface enhancing deployment speed.
Seamless Integration: Connects effortlessly with Microsoft services.
Security: Offers robust measures to protect data integrity.
Consistent Availability: Ensures continuous access to data worldwide.

Industries use Azure Cosmos DB to support business intelligence and IoT data management, using its capabilities for backend databases in web and mobile applications. The platform's scalability and real-time analytics benefit sectors like finance, healthcare, and retail, where managing diverse datasets efficiently is critical.

Microsoft

Sample Customers

Streak, Optiva, Mixpanel

TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify

Google Cloud Spanner vs. Microsoft Azure Cosmos DB