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)
14th
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 April 2026, in the Database as a Service (DBaaS) category, the mindshare of IBM Db2 on Cloud is 2.0%, up from 1.0% compared to the previous year. The mindshare of Microsoft Azure Cosmos DB is 4.7%, up from 1.4% 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.7%
IBM Db2 on Cloud2.0%
Other93.3%
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."
"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."
"The reliability is the most valuable feature. It is also user-friendly."
"The most valuable features of Microsoft Azure Cosmos DB include the TTL, the ability to scale up and down as needed, and geo-replication, which comes out of the box."
"The benefits of Microsoft Azure Cosmos DB were immediate for us."
"Cosmos is a PaaS, so you don't need to worry about infrastructure and hosting."
"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 is very 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."
"Cosmos DB makes life easier because if we want to use Mongo-type data, or Cassandra-type data, or maybe even just a simple cable storage-type data, then graph, there are multiple ways to do this."
"The peace of mind that Microsoft Azure Cosmos DB provides regarding global distribution is invaluable."
 

Cons

"I would give their support a ten if they had more tutorials available."
"Nobody is going to like the price."
"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."
"Azure Cosmos DB for NoSQL has a less developed interface and fewer SQL commands than MongoDB, and its community support is also smaller."
"One of our biggest pain points is the backup and restore functionality needs improvement. They've gotten a little better in this area. SQL Server's long-term retention is amazing, and you can restore data from years ago. You need to open a support Microsoft ticket to restore your Cosmos DB backup, and it comes in on a different Cosmos account. It's just kind of a headache to restore data."
"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."
"Azure Cosmos DB is generally a costly resource compared to other Azure resources. It comes with a high cost."
"There are no particular factors that need improvement. There is a little bit of a learning curve with scaling workloads, but it works smoothly."
"We'd like to avoid full DR replication if possible, as this would result in significant cost savings."
"An improvement would be a more robust functionality around updating elements on a document, or some type of procedural updates that don't require pulling the entire document."
"The built-in integration of the solution is tight."
 

Pricing and Cost Advice

Information not available
"Cosmos DB is expensive, and the RU-based pricing model is confusing. Although they have a serverless layer, there are deficiencies in what I can define and assign to a database. Estimating infrastructure needs is not straightforward, making it challenging to manage costs."
"Cosmos DB is a highly cost-optimized solution when used correctly."
"Pricing is one of the solution's main features because it is based on usage, scales automatically, and is not too costly."
"Cosmos should be cheaper. We actually intend to stop using it in the near future because the price is too high."
"You need to understand exactly the details of how the pricing works technically to stay within reasonable pricing."
"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 provides fair pricing."
"Its price is in the middle, neither too low nor too high."
report
Use our free recommendation engine to learn which Database as a Service (DBaaS) solutions are best for your needs.
886,576 professionals have used our research since 2012.
 

Top Industries

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

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.
886,576 professionals have used our research since 2012.