No more typing reviews! Try our Samantha, our new voice AI agent.

IBM Db2 on Cloud 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

IBM Db2 on Cloud
Ranking in Database as a Service (DBaaS)
15th
Average Rating
8.6
Reviews Sentiment
7.3
Number of Reviews
2
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 IBM Db2 on Cloud is 2.1%, up from 1.1% 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
ProductMindshare (%)
Microsoft Azure Cosmos DB4.8%
IBM Db2 on Cloud2.1%
Other93.1%
Database as a Service (DBaaS)
 

Featured Reviews

FM
Database Engineer at Meezan Bank
Multi-node architecture and it is good from a security point of view
I would rate the stability a seven out of ten. Most of the issues we faced during troubleshooting were due to specific bugs in the environment, and the only solution was to upgrade the database environment or services. But it is not easy to upgrade the database level when third-party applications are involved, as they are not always comfortable with upgrading. There should be some cumulative solution provided by IBM for their customers, just like other vendors. Upgrading to a certain version doesn't always resolve the issue. It might get resolved at the database level, but what about the other applications integrated with that database that are only compatible with older versions?
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 reliability is the most valuable feature; it is also user-friendly."
"The reliability is the most valuable feature. It is also user-friendly."
"Multiple business departments rely on reports and predictive analysis to make decisions for future business based on their data warehouse and Db2 network analytics tool. It helps our business department make decisions."
"Microsoft Azure Cosmos DB helped improve our organization's search result quality significantly when we started using it about eight years ago."
"The querying language and the SDKs they've provided over the years have been phenomenal, giving us a significant advantage."
"The solution is used because we get faster response times with large data sets than with SQL. It's essential for us because we have half a billion rows, and we need to return them quickly."
"The most valuable aspect of Cosmos DB is its performance."
"It gives us a lot of flexibility. The scaling is instantaneous as well. You immediately have all the resources available."
"Reading and inserting data into Microsoft Azure Cosmos DB is a very smooth process."
"We achieved a strong return on investment."
"Its wide support to the ecosystem is valuable. We can use this database with a lot of use cases, and that's one of the reasons why we prefer it. We have a lot of vendors, databases, and use cases, and wherever possible, we are trying to standardize databases. It is also secure."
 

Cons

"Nobody is going to like the price."
"I would give their support a ten if they had more tutorials available."
"In other environments like Oracle or Teradata, they provide their own solutions for troubleshooting issues. They provide built-in AI services or autonomous databases, which I don't see in the Db2 environment."
"For streaming platforms, Azure Cosmos DB could improve efficiency in data storage. Indexing can also be better. Enhanced capabilities are necessary to manage increased data amounts more effectively during searches."
"Better documentation on how to integrate with other components would be helpful because I was struggling with this."
"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."
"Microsoft Azure Cosmos DB's performance could be better. In large volumes of documents, the querying process becomes slow and complicated."
"The size of the continuation token in Azure Cosmos DB should be static rather than increasing with more data, as it can lead to application crashes. They should use a static key size."
"The query searching functionality has some complexities and could be more user-friendly. Improvements in this area would be very helpful."
"Our use case was a failure with Microsoft Azure Cosmos DB, and we do not have any other opportunity to use Microsoft Azure Cosmos DB."
"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."
 

Pricing and Cost Advice

Information not available
"The pricing model of Microsoft Azure Cosmos DB is a bit complex."
"Cosmos DB gave us three accounts for $400. We pay according to the usage."
"Cosmos DB is expensive compared to any virtual machine based on conventional RDBMS like MySQL or PostgreSQL."
"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."
"With heavy use, like a large-scale IoT implementation, you could easily hit a quarter of a million dollars a month in Azure charges if Cosmos DB is a big part of it."
"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."
"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."
"Cosmos DB's pricing structure has significantly improved in recent months, both in terms of its pricing model and how charges are calculated."
report
Use our free recommendation engine to learn which Database as a Service (DBaaS) solutions are best for your needs.
894,668 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
12%
Legal 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 Enterprise22
Large Enterprise58
 

Questions from the Community

What needs improvement with IBM Db2 on Cloud?
In other environments like Oracle or Teradata, they provide their own solutions for troubleshooting issues. They provide built-in AI services or autonomous databases, which I don't see in the Db2 e...
What advice do you have for others considering IBM Db2 on Cloud?
Since I have worked with almost every product, including IBM, Teradata is far better than any other data warehouse product. It's a separate database with its own features, architecture, and working...
What is your primary use case for IBM Db2 on Cloud?
It's a multi-node logical database clustered in three physical nodes. We use a lot of services already provided in our private cloud environment. It's a multi-node architecture.
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...
 

Also Known As

No data available
Microsoft Azure DocumentDB, MS Azure Cosmos DB
 

Overview

 

Sample Customers

Owens-Illinois, KONE Corp., Cambridgeshire Fire and Rescue, Canon Europe, Delhaize America, Wimbledon
TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
Find out what your peers are saying about IBM Db2 on Cloud vs. Microsoft Azure Cosmos DB and other solutions. Updated: April 2026.
894,668 professionals have used our research since 2012.