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

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 (4th)
Oracle Exadata Cloud at Cus...
Ranking in Database as a Service (DBaaS)
12th
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 June 2026, in the Database as a Service (DBaaS) category, the mindshare of Azure Database for PostgreSQL is 3.7%, up from 1.3% compared to the previous year. The mindshare of Oracle Exadata Cloud at Customer is 3.5%, down from 4.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Database as a Service (DBaaS) Mindshare Distribution
ProductMindshare (%)
Azure Database for PostgreSQL3.7%
Oracle Exadata Cloud at Customer3.5%
Other92.8%
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

"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."
"Backups are easy, resizing is quick, and the query analyzers help me find out what's happening in each of the queries."
"Azure Database for PostgreSQL has influenced my application development process by enabling me to take some of what we used to do on-premises, with PostgreSQL hosted in virtual machines, and transition that process into a SaaS solution."
"Overall, Azure Database for PostgreSQL has been good for us."
"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."
"If a client is looking to check these boxes—performance, speed, reliability, and resiliency in general—knowing that it will satisfy application needs not just today but in the future, it is definitely a choice."
"Automatic patching and backups have a huge impact on my database management strategy—we have an operations team of two people and do not have time to handle database maintenance manually, so we chose platform-as-a-service for this reason."
"In terms of integration, we already have SharePoint online, and we're starting to explore PowerApps and PowerFlow. It's all seamless. The ease of integrating SQL and licensing purposes plays a significant role, making it a comfortable choice for the organization."
"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."
"I am particularly fond of the intelligent capabilities that enhance the backend, utilizing technology to analyze SQL queries."
"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."
"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."
"We have migrated mission-critical databases to Exadata and gained significant performance in our OLTP and Batch jobs."
"The operation model is the most valuable feature."
 

Cons

"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."
"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."
"They can offer more RAG extensions. Currently, it only has the vector search."
"Occasionally, we experience throughput issues due to bandwidth limitations of client setups with Azure, which have limited connections, but as far as the service itself goes, it has been rock solid."
"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."
"Azure Database for PostgreSQL can be improved in ways I'm very curious to explore with Horizon."
"In the future, I would like to see anomaly detection."
"Azure Database for PostgreSQL has not really helped reduce infrastructure costs at my company."
"Scalability is not straightforward."
"For the data migration, we used ZDM. It was not integrated with the databases, and the documentation lacks clarity."
"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."
"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."
"Today their support no longer lives up to my expectation."
"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."
 

Pricing and Cost Advice

"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."
"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."
"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 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."
"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.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Comms Service Provider
11%
Manufacturing Company
11%
Marketing Services Firm
10%
Financial Services Firm
34%
Insurance Company
9%
Manufacturing Company
8%
University
5%
 

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: June 2026.
900,644 professionals have used our research since 2012.