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

Microsoft Azure Cosmos DB vs Oracle Exadata Cloud at Customer 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

Microsoft Azure Cosmos DB
Ranking in Database as a Service (DBaaS)
3rd
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
110
Ranking in other categories
NoSQL Databases (1st), Managed NoSQL Databases (1st), Vector Databases (1st)
Oracle Exadata Cloud at Cus...
Ranking in Database as a Service (DBaaS)
13th
Average Rating
7.8
Reviews Sentiment
4.9
Number of Reviews
7
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Database as a Service (DBaaS) category, the mindshare of Microsoft Azure Cosmos DB is 4.9%, up from 2.8% compared to the previous year. The mindshare of Oracle Exadata Cloud at Customer is 3.3%, down from 4.1% 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.9%
Oracle Exadata Cloud at Customer3.3%
Other91.8%
Database as a Service (DBaaS)
 

Featured Reviews

Michael Hasenfang - PeerSpot reviewer
Director, Platform Engineering - Infrastructure Systems and Automation at a computer software company with 1,001-5,000 employees
Collecting compliance data has become more efficient while managing unstructured inputs for reporting
The features that I find most valuable within Microsoft Azure Cosmos DB are probably the cost, as the cost optimization is good. The storage and queryability are good for what we're doing; it's a lot of unstructured data, so having a platform to put that in and then be able to harvest that data out for the reporting we do is essential. In terms of cost saving, it was probably easily 30 to 40% cheaper than doing a standard SQL, which is what we saw just on piloting and getting in there. We were initially thinking 20 to 25%, but we were probably more at the 35 to 40%. We are using Microsoft Azure Cosmos DB's hybrid search today. The value that it has added to my AI or search workloads is that I think it's optimized that process and made it easier. We have a lot of unstructured data coming from different dissimilar systems and different data sources, so correlating those things together and making sense of it has been very beneficial. Microsoft Azure Cosmos DB has had pretty good performance with searching through large amounts of data; it's been fast, and we haven't seen a lot of performance degradation while building larger queries and bringing in a large set of data. The dynamic auto-scale or serverless model from Microsoft Azure Cosmos DB has helped reduce costs and operational effort; however, it's hard to quantify how that plays out since you're using a shared service. It shifts my focus away from building, managing, and upgrading to adding value.
WB
Oracle DBS at Bpifrance
Positive experience with virtual cloud network creation and database migration highlights patching challenges
The best feature of Oracle Exadata Cloud at Customer is that it can be managed without needing only DBAs. We have many features, including the observability feature that helps check performance and generates numerous reports about performance. We have also implemented APIs, enabling us to create and perform many operations. This means we need DBAs who can work with APIs. We are autonomous in the patching process and don't need Oracle for patching. If you configure the process of patching, it will be executed automatically. We are using dynamic scaling which is implemented on an external virtual machine, helping us to downscale or upscale the CPU. Oracle Exadata Cloud at Customer has supported our organization's compliance and data sovereignty without problems. I have observed some limitations. For example, regarding encryption, though it is mandatory for Exadata Cloud at Customer, we cannot encrypt the database with external keys. Currently, with Exadata Cloud at Customer, using external keys is not possible.

Quotes from Members

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

Pros

"One of the nice features is the ability to auto-scale"
"The efficiency of search capabilities is significant, particularly when it comes to the flexibility of conducting in-depth, almost recursive searches that are both efficient and cost-effective."
"We doubled our productivity with this small application."
"The most valuable feature of the solution is that it is scalable with multiple master files."
"One valuable feature of Microsoft Azure Cosmos DB is partitioning. Its performance is very nice."
"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."
"As a NoSQL database, it offers schema flexibility which simplifies design and reduces initial engineering overhead."
"Our customer is very satisfied with it."
"I am particularly fond of the intelligent capabilities that enhance the backend, utilizing technology to analyze SQL queries."
"The most valuable feature is that it is based on Exadata infrastructure, which is Oracle 's leading engineered system that is trusted, fault-tolerant, and has unique performance features."
"I like that Oracle Exadata Cloud at Customer is a stable, well-positioned product in the market today, and it's very scalable."
"The best feature of Oracle Exadata Cloud at Customer is that it can be managed without needing only DBAs, with observability features to check performance, generate reports, and implement APIs for creating and performing many operations."
"Performance has significantly improved."
"Exporting and importing is easy because of its cleanliness, making the process easier. However, setting up the Data Guard was more difficult. Despite this, the client experienced lower downtime."
"The operation model is the most valuable feature."
"We have migrated mission-critical databases to Exadata and gained significant performance in our OLTP and Batch jobs."
 

Cons

"Once you create a database, it calls the container, and then items show up. 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."
"Areas of improvement for Microsoft Azure Cosmos DB include indexing. While it makes data retrieval easier, it also increases costs. If there's a better way to improve indexing at a lower cost, that would be really helpful, but that's the major point for now."
"It should offer a simple user interface for querying Microsoft Azure Cosmos DB."
"Performance issues do not occur frequently, but I occasionally face performance issues with Microsoft Azure Cosmos DB."
"Microsoft's support services are inadequate, especially during critical incidents."
"The first one is the ability to assign role-based access control through the Azure portal for accounts to have contributor rights."
"Customer service and technical support from Microsoft have been all right. On a scale of 1 to 10, I would give them probably a six, maybe a hard seven at most."
"The main downside I have faced was with hierarchical partitioning in Microsoft Azure Cosmos DB."
"Scalability is not straightforward."
"The solution is expensive."
"For the data migration, we used ZDM. It was not integrated with the databases, and the documentation lacks clarity."
"Oracle Exadata Cloud at Customer is stable, but the only problem occurs during OS patching. If you encounter issues, the VMC (virtual machine cluster) becomes unusable."
"We had some problems in the developer's environment. We had some problems with the initial installation environment."
"As a customer, you can't see the boot messages of your virtualized guest machines."
"A room for improvement in Oracle Exadata Cloud at Customer is that they need to train more partners to gain more knowledge because currently, they are keeping a lot to themselves. For example, they are still keeping a lot of information on their campus, so information sharing is limited."
"Today their support no longer lives up to my expectation."
 

Pricing and Cost Advice

"This cost model is beneficial because it allows for cost control by limiting resource units (RUs), which is ideal. However, for our needs, we can't engage with their minimum pricing, which ranges from 100 to 1,000 RUs. At the bare minimum, we need to use 4,000 RUs for a customer. I would like to find a way to gain some advantages from the lowest tier, particularly the ability to scale down if necessary. It would be helpful to have more flexibility in cost management at the lower end."
"Pricing is one of the solution's main features because it is based on usage, scales automatically, and is not too costly."
"The pricing and licensing model was initially difficult to understand, but as soon as I learned what was going on and how it was priced, it was pretty easy."
"Everything could always be cheaper. I like that Cosmos DB allows us to auto-scale instead of pre-provisioning a certain capacity. It automatically scales to the demand, so we only pay for what we consume."
"The pricing model of Microsoft Azure Cosmos DB is a bit complex."
"The Cosmos DB pricing model, initially quite complicated, became clear after consulting with Azure Advisor, allowing us to proceed with confidence."
"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."
"Pricing, at times, is not super clear because they use the request unit (RU) model. To manage not just Azure Cosmos DB but what you are receiving for the dollars paid is not easy. It is very abstract. They could do a better job of connecting Azure Cosmos DB with the value or some variation of that."
"The price is too much."
"The machine and the cloud model itself already have licensing advantages."
report
Use our free recommendation engine to learn which Database as a Service (DBaaS) solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Legal Firm
11%
Comms Service Provider
8%
Manufacturing Company
8%
Financial Services Firm
31%
Manufacturing Company
9%
Insurance Company
9%
Educational Organization
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business33
Midsize Enterprise24
Large Enterprise58
By reviewers
Company SizeCount
Small Business4
Large Enterprise4
 

Questions from the Community

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...
What is your experience regarding pricing and costs for Oracle Exadata Cloud at Customer?
The pricing is reasonable due to a universal agreement, which often positions Oracle solutions better against others. I would rate the pricing an eight out of ten.
What needs improvement with Oracle Exadata Cloud at Customer?
In future updates for Oracle Exadata Cloud at Customer, I would like to see another feature for the different costs for the non-CDB models, because if you are not using the non-CDB models, you have...
What is your primary use case for Oracle Exadata Cloud at Customer?
The use cases for Oracle Exadata Cloud at Customer are based on our actual solution. We have the Exadata, but it has reached its end of life. The X5 has attained the end of life, so we discussed mi...
 

Also Known As

Microsoft Azure DocumentDB, MS Azure Cosmos DB
No data available
 

Overview

 

Sample Customers

TomTom, KPMG Australia, Bosch, ASOS, Mercedes Benz, NBA, Zero Friction, Nederlandse Spoorwegen, Kinectify
IBVI, illycaffe, Scottish Water, trueblue, AirAsia, droptank
Find out what your peers are saying about Microsoft Azure Cosmos DB vs. Oracle Exadata Cloud at Customer and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.