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
Percona Server for MySQL
Score 9.7 out of 10
N/A
Percona Server for MySQL is a free, compatible, enhanced, open source drop-in replacement for MySQL. Percona states it provides superior performance, scalability, and instrumentation. Boasting over 5,300,000 downloads, Percona Server’s self-tuning algorithms and support for high-performance hardware delivers excellent performance and reliability Percona Server for MySQL delivers enterprise-grade features and higher uptime, along with a number of key benefits that…
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 …
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 …
It is a solution that complements those mentioned, and if we know the ecosystem of Percona tools, it is easier for us to learn the different options it offers.
Percona Server for MySQL Stacks up against all of these competitors. We choose Percona server for MySQL due to these reasons: open source, community support, scalability, and vendor locking. We were looking for an open-source database that is scalable and supported by the …
Performance and stability sets Percona Server for MySQL apart from the rest. Percona embraces the upstream version and contributes towards the upstream version making MySQL stronger on two fronts and thus having a much larger community. Many quality contributions have been made …
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.]
It is a good tool to carry out tests that measure the level of effectiveness of the database and it behaves well when, at the project level, we need to process large volumes of data in a massive way. It is not an optimal solution for applications oriented to the distribution of data between different machines.
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.
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.
A distributed database offering to scale writes with native sharding. Currently we make use of sharding managed by the application to scale writes. There is the option to place ProxySQL in front of the shards, but we need a true cloud native distributed option with an easy migration path. I would not say this is negative in terms of Percona Server for MySQL, but if Percona had a distributed database offering at some stage, we would follow Percona.
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.
Performance and stability sets Percona Server for MySQL apart from the rest. Percona embraces the upstream version and contributes towards the upstream version making MySQL stronger on two fronts and thus having a much larger community. Many quality contributions have been made by Percona into the base code. Percona provides great tools to support Percona Server for MySQL and this makes the monitoring and management easier
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.