Oracle Exadata is an enterprise database platform that runs Oracle Database workloads of any scale and criticality with high performance, availability, and security. Exadata’s scale-out design employs optimizations that let transaction processing, analytics, machine learning, and mixed workloads run faster. Consolidating diverse Oracle Database workloads on Exadata platforms in enterprise data centers, Oracle Cloud Infrastructure (OCI), and multicloud environments helps organizations increase…
$2.90
Per Unit
PostgreSQL
Score 8.8 out of 10
N/A
PostgreSQL (alternately Postgres) is a free and open source object-relational database system boasting over 30 years of active development, reliability, feature robustness, and performance. It supports SQL and is designed to support various workloads flexibly.
N/A
Pricing
Oracle Exadata
PostgreSQL
Editions & Modules
Database Server
$2.9032
Per Unit
Quarter Rack
$14.5162
Per Unit
No answers on this topic
Offerings
Pricing Offerings
Oracle Exadata
PostgreSQL
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Oracle Exadata
PostgreSQL
Considered Both Products
Oracle Exadata
Verified User
Anonymous
Chose Oracle Exadata
I couldn’t find all the options listed here, so I’m
summarizing the ones we considered during our evaluation before selecting
Oracle Exadata Service on AWS:
A unique architecture of Oracle Exadata machine which consists of several components: compute, storage cells with offloaded SQL processing within the cell, smart cache. In addition it is an Oracle RAC server with high speed interconnect between its built-in nodes.
Oracle Database Exadata Cloud Service allocates built-in cloud automation and enhances enterprise-class business continuity by enhancing zero downtime maintenance which is contrary to other alternatives such as Apache Hive.
Vice President, Chief Architect, Development Manager and Software Engineer
Chose Oracle Exadata
Oracle Exadata Database Machine had the best performance overall hands down. It clearly beat the competition and we were seeing 1000X improvement on SAP HANA. Oracle Exadata Database Machine beat that without us refactoring our code. To achieve that in HANA, we had to …
IBM POWER System is a general purpose hardware optimize to runs various software with high-performance resource intensive operations. On the other hand, Oracle Exadata Database Machine is specifically engineered to run Oracle Database software efficiently, this combination of …
IBM AIX and HP-UX implementations of Oracle database solutions have a lot of performance issues. Both do not provide as much robust configuration customization as Exadata. Hardware support is limited. There is generally a long delay between hardware update being certified with …
We have done a proof of concept for both and have seen a lift with our batch processing and all other aspects with Oracle Exadata. Oracle Exadata storage servers have been playing a key role with the overall success compared to other products.
We selected it just from a performance perspective, and that the ROI with the Oracle Exadata Database Machine is bigger than other machines. You can run with it for at least 5 years.
I do not think there is any alternative for Exadata. Flash storage or SSD can not solve the IO bottleneck issues the way Exadata handles the IO subsystem.
Exadata beats the competition because the smart scan and offloading technology is more about software than hardware, so you cannot just buy a beefy server and add flash disks to compete. The Exadata software is what makes it special.
My expirence with other solutions is very limited, but what I saw/heard is, that on Azure the managed MS SQL Server is said to be more flexible and you can use it in a serverless-ish fashion. But on the other hand, PostgresSQL is still strong regarding its efficiency. And in my …
Being open source, PostgreSQL offers the highest performance among its peers. It has a strong support community where we can find solutions to most of the queries. It's suited for GIS (Geospatial) based applications, making it unique from its peers. There are fewer databases …
PostgreSQL holds it own against both these options. Some of these DBs are in play for certain needs but the majority are PostgreSQL because of cost and operational performance.
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
MySQL is an Oracle product which has in itself some known issues due to that (support, contract terms). Based on my knowledge, PostgreSQL support everything that MySQL support (syntax wise) and it adds more improvements and syntaxes that make the life of database engineers and …
First It's open source and it's cost-effective compared to other databases.PostgreSQL can be easily integrated with numerous platforms. It is well known and appreciated so relying on it as our system database can be easily accepted by our customers. And if your developing a …
For our use cases, PostgreSQL is just as feature rich as other options, costs less, and is simple to get up and running. There is also a plethora of documentation to support it which makes it a great option for a small scale startup without needing high levels of expertise to …
In this case, Postgres is preferred because it handles large data sets and requires fewer hardware resources than its competitor, MySQL. Compared to PostgreSQL, Microsoft products are excellent, but the installation process for MS SQL is lengthy. PostgreSQL has an advantage …
I've been using different databases for the past 20 years, solutions like MS SQL Server, MySQL, MariaDB, Interbase, Firebird, DB2, etc., and by using them I wasn't able to be neither close to the performance PostgreSQL deliver. Also, it is one of the most popular databases on …
Although the competition between the different databases is increasingly aggressive in the sense that they provide many improvements, new functionalities, compatibility with complementary components or environments, in some cases it requires that it be followed within the same …
We evaluated both PostgreSQL and MySQL, two popular open source relational databases. While they are very similar in most areas, PostgreSQL's reliability and performance won us over, plus it has much better support from cloud vendors we also work with.
Postgres stacks up just [fine] along the other big players in the RDBMS world. It's very popular for a reason. It's very close to mySQL in terms of cost and features - I'd pick either solution and be just as happy. Compared to Oracle it is a MUCH cheaper solution that is just …
A free corporate professional product. Who does not want to have such a thing, we hesitated because we did not know the product before and frankly we did not want it at first. But when we give it a chance, it has been running smoothly for years.
When we were originally evaluating Redshift we ran into some issue with dates. Either way, Postgres is a better choice than Redshift because it avoids vendor lockin. We ended up choosing Postgres over MySQL because it was easier at the time to get a hosted Postgres cluster up …
As I have been telling all along, PostgreSQL is much cheaper compared to the other RDBMS solutions. It has got better performance with some of the application services that we are using and is easy to maintain. Overall, we are satisfied migrating to PostgreSQL database clusters.
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also …
Its main characteristic is the integrity of the data. In addition, being free software, it has no costs associated with its license, which allows the number of installations to be scaled without problems.
The technical staff quickly learns about its installation, configuration …
Both Oracle and MS-SQL database option fell when we evaluated the effect on our overall solution cost to our customers. customer examine the overall cost of the solution they buy, selecting Oracle or MS-SQL would leave less money in our pockets. We are Linux based solutions and …
PostgrPostgreSQL as a transaction db engine against oracle and sql server works well. TPM wise compared to MySQL and MariaDB, on an evan scale. SQL function supports, far outweighs compared to MySQL and MariaDB. PG Extensions allow for flexibiltity and scalability. Allows …
We selected PostgreSQL due to the number of employees who have used it in the past. The data consistency guarantees. The multiple transaction isolation levels support.
PostgreSQL outperforms every other option. It is faster, more flexible, more reliable, easier to maintain, and more consistent in behaviour than any of the other offerings.
The main reason for select PostgreSQL against MS SQL Server Express edition is the necessity to use open-source platform, without any issues for licensing, client licensing, etc. etc, which is usually follows developers and project managers when they start to use products and …
First, get the database on Oracle. If you are in an Oracle stack, it would be much better to use the Oracle products. If you are driving a Ferrari, you wouldn’t put a Mercedes engine in it. If you are writing a query, you cannot rely on other brands. Since I'm an architect, when I look for a product, I look for performance.
The installation is easy because it comes out-of-the-box and you just start using it.
Previous to Oracle Exadata, we were using a normal Oracle RAC service. We were just waiting for this product to come out.
I'm currently writing a data warehouse on Exadata. Before this solution, we were aiming for this to be completed by 8 a.m., when our ETLs would finish. With the help of Exadata's special features, this was reduced to 3 a.m. This solution allows us to bring more data within the same time period. It provides us with more subject areas that provide more reports to our users. Our ETL times reduced to 65%, then to 50%.
Based on my experience, PostgreSQL is exactly what I imagine when thinking of a relational database: it is fast for querying and intuitive (if the underlying relations have been well written) and its writes are also efficient. Of course you need to know that a relational database is what you need, for example I would not recommend it if you have a lot of unstructured data that have no way to create a relation from and if you need to run heavy aggregations over your data, as it is not where PostgreSQL would shine.
Customize-able for specific functionality optimized for combination of online transaction or analytical processing.
Ability to serve mix workloads with resource management feature enables prioritizing allocation for certain workload.
Scale-able on-premise with compatibility for cloud deployment offers flexible solution for organization considering to transition from on-premise solution.
The stability it offers, its speed of response and its resource management is excellent even in complex database environments and with low-resource machines.
The large amount of resources it has in addition to the many own and third-party tools that are compatible that make productivity greatly increase.
The adaptability in various environments, whether distributed or not, [is a] complete set of configuration options which allows to greatly customize the work configuration according to the needs that are required.
The excellent handling of referential and transactional integrity, its internal security scheme, the ease with which we can create backups are some of the strengths that can be mentioned.
The query syntax for JSON fields is unwieldy when you start getting into complex queries with many joins.
I wish there was a distinction (a flag) you could set for automated scripts vs working in the psql CLI, which would provide an 'Are you sure you want to do X?' type prompt if your query is likely to affect more than a certain number of rows. Especially on updates/deletes. Setting the flag in the headless(scripted) flow would disable the prompt.
Better documentation around JSON and Array aggregation, with more examples of how the data is transformed.
I am comparing Exadata with the Oracle RAC database experience. In addition to Oracle RAC features, Exadata provides automatic performance optimization through Smart Scan and storage indexes. Deep integration with the Oracle ecosystem and tight coupling with Oracle Enterprise Manager for monitoring and management. Some downsides of Exadata are: a steep learning curve, concepts like cell offloading, IORM, and flash cache behavior aren’t intuitive initially. Operating Exadata requires specialized DBA skills.
Postgresql is the best tool out there for relational data so I have to give it a high rating when it comes to analytics, data availability and consistency, so on and so forth. SQL is also a relatively consistent language so when it comes to building new tables and loading data in from the OLTP database, there are enough tools where we can perform ETL on a scalable basis.
The data queries are relatively quick for a small to medium sized table. With complex joins, and a wide and deep table however, the performance of the query has room for improvement.
There are several companies that you can contract for technical support, like EnterpriseDB or Percona, both first level in expertise and commitment to the software.
But we do not have contracts with them, we have done all the way from googling to forums, and never have a problem that we cannot resolve or pass around. And for dozens of projects and more than 15 years now.
The online training is request based. Had there been recorded videos available online for potential users to benefit from, I could have rated it higher. The online documentation however is very helpful. The online documentation PDF is downloadable and allows users to pace their own learning. With examples and code snippets, the documentation is great starting point.
I couldn’t find all the options listed here, so I’m summarizing the ones we considered during our evaluation before selecting Oracle Exadata Service on AWS:
Continuing to use the Oracle RAC on‑premise database Running Oracle Database on AWS EC2 Using Oracle Database through the AWS RDS service
Since we wanted to retain Oracle RAC capabilities while achieving high performance and maintaining our presence in the AWS public cloud, we selected the Oracle Database @AWS Exadata service.
In my experience using all of these products over many years, PostgreSQL is better than any of them in reliability, performance, productivity, cost, scalability and interoperability across operating systems.
One of the central critical systems was migrated from a large 4-node Oracle RAC running on legacy hardware. This application was experiencing severe performance issues literally causing loss of service for numerous customers. Once it was migrated to a 2-node Exadata server, its average performance improved almost by a level of magnitude, therefore eliminating any signs of application slowness.
Numerous application databases were migrated to Exadata servers which reduced the overall cost of hardware due to Exadata's price structure.