Try our new research platform with insights from 80,000+ expert users

Azure Database for PostgreSQL vs Oracle Exadata Cloud at Customer comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 18, 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

Azure Database for PostgreSQL
Ranking in Database as a Service (DBaaS)
5th
Average Rating
8.8
Reviews Sentiment
6.3
Number of Reviews
23
Ranking in other categories
Open Source Databases (5th)
Oracle Exadata Cloud at Cus...
Ranking in Database as a Service (DBaaS)
9th
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 January 2026, in the Database as a Service (DBaaS) category, the mindshare of Azure Database for PostgreSQL is 3.3%, up from 0.3% compared to the previous year. The mindshare of Oracle Exadata Cloud at Customer is 3.7%, down from 4.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Database as a Service (DBaaS) Market Share Distribution
ProductMarket Share (%)
Azure Database for PostgreSQL3.3%
Oracle Exadata Cloud at Customer3.7%
Other93.0%
Database as a Service (DBaaS)
 

Featured Reviews

Sathish Palanisamy - PeerSpot reviewer
Staff Data Engineer at a transportation company with 10,001+ employees
Improves database performance, supports AI integration, and accelerates customer-focused innovation
Azure Database for PostgreSQL can be improved in the area of elastic capabilities. One of the things we were actively looking for is the elastic feature, which was made a GA at this Ignite event. I am really happy that finally in Azure, we have a product which we can use for elastic clusters. If you are bound with a single server, then you have a vertical limit. Now you do not have any limits. As long as your use case grows, we can grow. The only thing I would maybe be thinking about is we should also allow customers to pick different node sizes for every node inside the elastic eventually. Some nodes do not need that big capacity. So that may be a nice-to-have feature, though it is not a must-have at this point.
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

"PostgresSQL is acknowledged as an incredibly powerful industry leader. We've built critical pieces of national infrastructure in the UK that rely on Postgres. A version of Postgres on Azure that's easy to adopt enables us to innovate. The addition of AI extensions is even more exciting. It's a significant opportunity for us."
"We transact 128 trillion data per month using Azure Database for PostgreSQL, which helps us to be more successful on every transaction that the customer is requesting from us."
"Our organization's database uptime has improved after implementing Azure Database for PostgreSQL, particularly with the flexible server's redundant configuration capabilities, which allow for failovers and read-only configurations."
"The most valuable features of Azure Database for PostgreSQL for us are reliability, performance, and cost, making it a good cost-benefit for us."
"A native cloud approach actually has more advantage because it is easy to deploy, faster to deploy, and easy to recover and roll back."
"The performance of our RAG application is very good. We have 96% satisfaction."
"The operational efficiency of Azure Database for PostgreSQL is good."
"The benefits we have realized as a company from using Azure Database for PostgreSQL on Azure make the life of our customers and our solution easier."
"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 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."
"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."
"Performance has significantly improved."
"The operation model is the most valuable feature."
"I like that Oracle Exadata Cloud at Customer is a stable, well-positioned product in the market today, and it's very scalable."
"I am particularly fond of the intelligent capabilities that enhance the backend, utilizing technology to analyze SQL queries."
 

Cons

"Support can certainly get better."
"The critical service is the Azure OpenAI service. It would help to make it simpler and easier to integrate with that or cognitive services."
"They can offer more RAG extensions. Currently, it only has the vector search. It does not presently support knowledge graph functionalities as Neo4j does. It also does not offer some tools to improve indexing the way other vector databases offer."
"Perhaps a minor improvement could be made in simplifying user additions, allowing for an easier process rather than scripting it out. However, scripting is not a significant issue."
"Coming from a traditional Oracle Exadata setup, all queries will run faster because Oracle has that optimization layer in between which optimizes it for you, which is why you pay a lot of money for that. When you come to Azure Database for PostgreSQL, that layer is gone."
"Microsoft support for Azure Database for PostgreSQL rates about four out of ten based on my experience. You always get the same questions with Microsoft support, and it's not really straightforward."
"They can offer more RAG extensions. Currently, it only has the vector search."
"We had to move to a CSP. This has been a significant challenge. We experienced trouble with our CSP and had to change CSPs because we could not get the level of support we needed from them."
"We had some problems in the developer's environment. We had some problems with the initial installation environment."
"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."
"The solution is expensive."
"Scalability is not straightforward."
"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."
"For the data migration, we used ZDM. It was not integrated with the databases, and the documentation lacks clarity."
 

Pricing and Cost Advice

"We do not pay for a full-year subscription because our usage is still at the beginning phase and not much. The pay-as-you-go model works well for us."
"The pay-as-you-go pricing model plays a critical role in managing database-related costs and resource allocation. We build using Infrastructure as Code (IAC) and maintain a focus on FinOps to control Azure service costs. Some clients are pushy on price. It's critical to automate it, so we're just using it when appropriate and switching it off in certain scenarios."
"The pricing experience is positive. Azure Database for PostgreSQL reduces the need for hardware investments, and the pay-as-you-go pricing model positively affects database-related costs by allowing us to start small and scale as needed."
"There aren't any notable areas for improvement that I could see. PostgreSQL was self-sufficient with no need for additional database knowledge to maintain it."
"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.
881,082 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
14%
Marketing Services Firm
12%
Educational Organization
9%
Financial Services Firm
35%
Manufacturing Company
13%
Computer Software Company
8%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise4
Large Enterprise16
By reviewers
Company SizeCount
Small Business4
Large Enterprise4
 

Questions from the Community

What is your experience regarding pricing and costs for Azure Database for PostgreSQL?
My experience with pricing, setup costs, and licensing for Azure Database for PostgreSQL is positive; I appreciate it all. The pricing is very cost-effective and stable given that we have many data...
What needs improvement with Azure Database for PostgreSQL?
Azure Database for PostgreSQL can be improved in ways I'm very curious to explore with Horizon. I'm interested in seeing how the fully enterprise-hardened features change things and where that blur...
What is your primary use case for Azure Database for PostgreSQL?
My main use cases for Azure Database for PostgreSQL came from a personal project to scratch an itch, and it was the easiest one to go grab. I appreciate how easy PostgreSQL is to get running locall...
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...
 

Overview

 

Sample Customers

Information Not Available
IBVI, illycaffe, Scottish Water, trueblue, AirAsia, droptank
Find out what your peers are saying about Azure Database for PostgreSQL vs. Oracle Exadata Cloud at Customer and other solutions. Updated: December 2025.
881,082 professionals have used our research since 2012.