EDB Postgres Advanced Server vs. GraphQL

Very well suited to applications mixing relational with NoSQL and/or complex data types, such as network analysis, JSON, key-value-pair, etc. Excellent if you have multiple programming languages in use (Python, Perl, R, etc.) because PPAS supports so many languages natively. Not well suited if you need encryption at rest, compressed data or very large database-tier backups. [Large backups should be done at the storage tier if possible.]

Incentivized

• 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.

Incentivized

• 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.

Incentivized

We chose Postgres Plus Advanced Server because we had the finances to do so and needed the robust featureset, along with the power to optimize our performance and integrate with the development tools of our choosing. We audited a number of options, exploring potential solutions at various levels of robustness and decided that this was our best option moving forward.

Incentivized

• 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.

Incentivized