Percona Server for MySQL

We are using Percona Server for MySQL along with other solutions oriented to managing NoSQL databases such as MongoDB and others oriented to documents such as ElasticSearch.This tool complements other tools in order to complete the lifecycle of applications and measure their performance in different environments.

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.

Percona Server for MySQL is being used by the technology department for storing information regarding our customers, products, and other entities.

It is well suited for setting up reliable and secure database servers with all the advantages of an RDBMS.
Like every RDBMS, horizontal scaling could be a problem for Percona.

We migrated to Percona Server for MySQL from another database solution, Postgres. I lead a startup team, housed within a larger organization, and presently Percona Server for MySQL is used for our team. We are working on an EdTech product, and Percona Server for MySQL is used to store, analyze, and work with user information. Our aim is fast querying, easy deployment, and good support.

A modern day MySQL/RDBMS solution, where scalability is a pain point, logging is critical, performance is a bottleneck, and you're going to mostly work with the cloud. While it's relatively newer as opposed to more traditional offerings, it is catching up fast in features and support

Percona Server for MySQL is being used as a primary OLTP database in my current organization. We are using it across the whole organization (across the group of companies). Percona Server for MySQL is solving our problems to store and retrieve data in a high transactional environment.

Percona Server for MySQL is best suited for any RDBMS workload(OLTP/OLAP). It's a drop-in replacement of MySQL. As of now, it lacks inbuild HA feature.

Percona Server for MySQL is being used across our whole organization. We are running 50+ primary instances in our data center with DR replica's running on compute instances inside GCP in 2 different regions. Percona Server for MySQL solves our need for well-tested and stable MySQL instances with Percona doing additional testing to the upstream releases which gives that added level of stability that we need for the massive volumes of processing as well as the required performance in sharded instances.

Percona Server for MySQL covers 100% of our requirements in terms of our OLTP traffic and provides the High Availability levels required through a typical primary and 2 replica's using semi-synchronous replication. We're able to scale our writes using sharding, but a true distributed database would be a great option on top of this. In terms of OLAP traffic, we leverage columns stores available, but Percona Server fairs well.