The EDB Postgres Advanced Server is an advanced deployment of the PostgreSQL relational database with greater features and Oracle compatibility, from EnterpriseDB headquartered in Bedford, Massachusetts.
N/A
Oracle Autonomous Data Warehouse
Score 8.2 out of 10
N/A
Oracle Autonomous Data Warehouse is optimized for analytic workloads, including data marts, data warehouses, data lakes, and data lakehouses. With Autonomous Data Warehouse, data scientists, business analysts, and nonexperts can discover business insights using data of any size and type. The solution is built for the cloud and optimized using Oracle Exadata.
N/A
PostgreSQL
Score 8.7 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.
PPAS proved better for our customer's data-centric apps than Oracle in all but a few edge cases (encryption at rest and multi-TB database-tier backups) because it is simpler to install/maintain, runs nearly all Oracle-syntax SQL as well as ANSI SQL. PPAS has much more JSON …
Reason to select Oracle Data Warehouse are mentioned below: 1. If some of your old process are already setup using Oracle Data Warehouse 2. High user community, which make solving doubt using internet very easy
It's great if you are using or wish to use PostgreSQL and need the added performance optimization, security features and developer and DBA tools. If you need compatibility with Oracle it's a must-have. There are many developer features that greatly assist dev teams in integrating and implementing complex middleware. It's great for optimizing complex database queries as well as for scaling. I would recommend Postgres Plus Advanced Server for any software development team that is hitting the limit of what PostgreSQL is capable of and wants to improve performance, security, and gain extra developer tools.
II would recommend Oracle Autonomous Data Warehouse to someone looking to fully automate the transferring of data especially in a warehouse scenario though I can see the elasticity of the suite that is offered and can see it is applicable in other scenarios not just warehouses.
PostgreSQL is best used for structured data, and best when following relational database design principles. I would not use PostgreSQL for large unstructured data such as video, images, sound files, xml documents, web-pages, especially if these files have their own highly variable, internal structure.
PPAS Oracle compatibility, especially the PL/SQL syntax, has made migrating database-tier code very simple. Most Oracle packages do not need to be changed at all and those that do are generally for simple reasons like a reserved word in PPAS that is allowed in Oracle.
PPAS xDB, the multi-master replication tool, is simple and - most important - does not break with network or other interruptions. We have been able to configure and forget, which our customers could never do with other multi-master tools.
Most people had no idea that PPAS and PostgreSQL have full CRUD support for JSON. They think you need a specialized product and/or that JSON is read-only. Every organization that I have worked with is evaluating adding JSON to their relational model.
Very easy and fast to load data into the Oracle Autonomous Data Warehouse
Exceptionally fast retrieval of data joining 100 million row table with a billion row table plus the size of the database was reduced by a factor of 10 due to how Oracle store[s] and organise[s] data and indexes.
Flexibility with scaling up and down CPU on the fly when needed, and just stop it when not needed so you don't get charged when it is not running.
It is always patched and always available and you can add storage dynamically as you need it.
Documentation is excellent but spread out across many resources and can take a while to wade through—would benefit from having more intro level, getting started guides for various languages.
Ruby support is excellent but more Ruby examples and beginner-level documentation would be nice.
It is sometimes hard to find a community of users on StackOverflow so a larger community, and a dedicated forum with active members to answer questions and work through issues would be nice.
It is very expensive product. But not to mention, there's good reasons why it is expensive.
The product should support more cloud based services. When we made the decision to buy the product (which was 20 years ago,) there was no such thing to consider, but moving to a cloud based data warehouse may promise more scalability, agility, and cost reduction. The new version of Data Warehouse came out on the way, but it looks a bit behind compared to other competitors.
Our healthcare data consists of 30% coded data (such as ICD 10 / SNOMED C,T) but the rests is narrative (such as clinical notes.). Oracle is the best for warehousing standardized data, but not a good choice when considering unstructured data, or a mix of the two.
Does not require continous attention from the DBA, autonomous features allows the database to perform most of the regular admin tasks without need for human intervention.
Allows to integrate multiple data sources on a central data warehouse, and explode the information stored with different analytic and reporting tools.
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.
Understanding Oracle Cloud Infrastructure is really simple, and Autonomous databases are even more. Using shared or dedicated infrastructure is one of the few things you need to consider at the moment of starting provisioning your Oracle Autonomous Data Warehouse.
PPAS proved better for our customer's data-centric apps than Oracle in all but a few edge cases (encryption at rest and multi-TB database-tier backups) because it is simpler to install/maintain, runs nearly all Oracle-syntax SQL as well as ANSI SQL. PPAS has much more JSON capabilities (full CRUD vs. read-only in Oracle), simpler geospatial, simpler / more stable replication and datatypes that match developer expectations, such as BOOLEAN and ENUMs.
As I mentioned, I have also worked with Amazon Redshift, but it is not as versatile as Oracle Autonomous Data Warehouse and does not provide a large variety of products. Oracle Autonomous Data Warehouse is also more reliable than Amazon Redshift, hence why I have chosen it
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 family of applications that performs the company that develops it and that is not all bad, but being able to adapt or configure different programs, applications or other environments developed by third parties apart is what gives PostgreSQL a certain advantage and this diversification in the components that can be joined with it, is the reason why it is a great option to choose.
Postgres Plus Advanced Server is quite complex and may take longer to implement certain things than simply using PostgreSQL depending on developer familiarity with the platform.
Getting up to speed can be daunting so again, there is an upfront cost in time spent learning the platform, besides the potential for extra time spent on a feature-by-feature basis.
The cost of Postgres Plus Advanced Server should be weighed against simply using PostgreSQL to decide which is the best solution for your business needs.
Overall the business objective of all of our clients have been met positively with Oracle Data Warehouse. All of the required analysis the users were able to successfully carry out using the warehouse data.
Using a 3-tier architecture with the Oracle Data Warehouse at the back end the mid-tier has been integrated well. This is big plus in providing the necessary tools for end users of the data warehouse to carry out their analysis.
All of the various BI products (OBIEE, Cognos, etc.) are able to use and exploit the various analytic built-in functionalities of the Oracle Data Warehouse.
Easy to administer so our DevOps team has only ever used minimal time to setup, tune, and maintain.
Easy to interface with so our Engineering team has only ever used minimal time to query or modify the database. Getting the data is straightforward, what we do with it is the bigger concern.
