Percona Server Reviews

My main use case for Percona Server was for an e-commerce platform, operating as a webshop. The customer had a migration underway where they wanted to move from a certain service provider to managing things themselves. They previously used MariaDB, which did not work, so we needed to move to MySQL, and Percona has a MySQL derivative that worked for us. The use case also involved running this within a Kubernetes cluster.

A specific example of how Percona Server was used in that e-commerce platform is that the state was managed through the database, and the entire hydration process occurred there as well. We had server-side rendering happening, and the client-side renders were hydrated through whatever lived in Percona Server database, which resulted in a huge amount of read operations. For redundancy and performance reasons, we worked with about three instances of Percona Server running to ensure that we got the read performance we needed. One issue was the contention and locking that occurred during write operations, and this is where I think Percona showcased that their system was better than other MySQL derivatives.

We used Kubernetes installed on VPS in Hetzner for that project, and it was very important for us to have a platform that was MySQL compliant, along with all the CRDs, the custom resource definitions, required to use it properly in Kubernetes. We also needed support in managing the service, so having a specialist to tweak those parameters for good database performance was really good to have.

My experience with the Kubernetes-native features was that getting it into Kubernetes was really easy. It is just a Helm chart that you throw in there, and it kind of works. Of course, Helm charts have many intricacies, so parameterizing it correctly was essential, but it provided an out-of-the-box experience for getting it into our cluster.

A cool thing to call out is that they have an observability dashboard for Grafana to see what is going on, which works seamlessly. It is not just about getting everything in there, but also having visibility into how it works, and we had lots of interesting metrics available to use.

Percona Server offers excellent features including its compliance with the MySQL/Maria dialect, which was essential for our existing application. We faced the challenge of deploying it redundantly in a way that ensured the application would work now and in the future, which involved different replication strategies. Additionally, we needed it to be Kubernetes-native with an operator to check if the database was running and to manage redeployments. Percona provided all of that, along with optimization recommendations from a specialist. There were not many alternatives available, and we also wanted to stay on an open-source stack, which Percona supports to keep everything transparent while providing support as well.

Impact of Percona Server on my organization has been positive. The database was a mess and did not run well, and we suffered a loss of revenue in that project. The website needed to work, as it was a legacy system with lots of Java applications depending on it. If that database did not work, the website could not even start up, making it extremely important for the e-commerce side to have a well-functioning database.

After switching to Percona Server, we were able to resolve those issues quickly. The platform originally worked with MariaDB, so we spent about three months refactoring the software to accommodate features that MariaDB does not support or supports differently compared to MySQL dialect. The implementation for Percona Server took less than a month, and we have not encountered issues since then.

Percona Server seems great to me overall. If I had to think of any small area for improvement for Percona Server, it would be around the proxy story. When adding a proxy to manage traffic better, we first tried SQL Proxy, but it never really worked for us, which was unfortunate because SQL Proxy offers better optimizations for read performance. We did have success with HAProxy, but it works on a network level, while SQL Proxy was designed to be SQL-aware and distribute parts of the query across the database cluster. The performance gain we were hoping for with SQL Proxy did not materialize, so we remained on the network level with HAProxy.

Databases can be finicky regarding the performance they need. We had some disk I/O latency issues, which led us to use different types of nodes in our Kubernetes cluster where we provisioned Percona Server explicitly. There is a lot of IOPS happening under the hood, and while I suspect the application was not very efficient, it was also challenging to identify that we were experiencing performance issues due to disk performance. It would be helpful to clarify the metrics related to disk I/O latency so we could understand where our bottlenecks are.

I used Percona Server in a project for about a year.

Percona Server is stable.

Percona Server's scalability is great, which is its core feature.

Percona Server's customer support is excellent with very responsive and friendly service.

We initially struggled with getting MariaDB working, which took a team of six people several months. This was time wasted, whereas with Percona Server, once it is up and running, you really have to do very little.

We evaluated different solutions such as MariaDB and MySQL, but we only evaluated them without implementing them. Our experience with MariaDB was that it did not work for us.

My advice for others looking to use Percona Server is that while it is a great product for making things work, it does not eliminate the need for a database administrator. You still need to know what you are doing, and it can alleviate a lot of the pain of running a database. However, it does not equate to a fully managed database, at least in our use case where we run it in our own Kubernetes cluster. That knowledge is also beneficial when working with a consultant for setup and database optimization.

I was involved on the sideline when it comes to pricing, setup cost, and licensing. I think the pricing was good. What I appreciated was that they packaged support with the licenses, ensuring that we ended up with a working database, which is powerful because it shows that they are focused on solving a problem rather than just selling a product.

We evaluated different solutions such as MariaDB and MySQL, but we only evaluated them without implementing them. Our experience with MariaDB was that it did not work for us.

My advice for others looking to use Percona Server is that while it is a great product for making things work, it does not eliminate the need for a database administrator. You still need to know what you are doing, and it can alleviate a lot of the pain of running a database. However, it does not equate to a fully managed database, at least in our use case where we run it in our own Kubernetes cluster. That knowledge is also beneficial when working with a consultant for setup and database optimization. If you want to go open-source and are knowledgeable about databases, Percona Server is great and will provide everything you need. But if you are looking for a solution without needing to understand databases, this might be too advanced. I would rate this product an 8 overall.

Percona Server is used on a master-master cluster for Airflow.

Percona Server is used because it is useful for distributing the workload on Airflow, which is a scheduling workflow engine for scheduling jobs.

Performance improvements are delivered largely through features such as XtraBackup, which support these advancements.

The monitoring tool of Percona Server is very good.

Percona Server positively impacts the organization because it is free and open-source.

Being open-source significantly helps with cost savings and lowers the costs that had to be paid for enterprise licensing for MySQL with Oracle.

The introduction of materialized views in Percona Server would be a significant help, as this feature has been requested for a long time.

Percona is a drop-in replacement for MySQL, with XtraBackup being a killer feature, as it provides non-locking backup, and PMM is a complete monitoring solution. The overall review rating for Percona Server is 7.

Percona Server is my main solution for electronic information systems, and I use Percona XtraDB Cluster for this purpose.

Percona Server has facilitated the configuration of clusters compared to using a large cluster setup.

Percona Server helps me maintain consistency in my systems.

Percona Server offers excellent scalability and easy configuration.

The configuration feature is particularly valuable to me because adding a new server requires minimal effort, which streamlines my workflow.

Database consistency is the most important feature for me.

Percona Server has positively impacted my organization by reducing downtime for applications and improving backup capabilities.

Percona Server has improved downtime and backup management by making it easy to switch to another server when necessary, and it includes built-in backup functionality.

Percona Server could be improved by adding more advanced query fields, which would be very helpful.

I have been using Percona Server for more than eight years.

Percona Server is very stable.

Percona Server's scalability is easy to configure.

I previously used the free version of MySQL before switching to Percona Server.

I would advise others looking into using Percona Server that it is very good and safe, as well as being easy to set up.

I have not seen a return on investment since I am using the free version.

My experience with pricing, setup cost, and licensing is that I am using the free version.

My main use case for Percona Server is deploying the community version without support to MongoDB servers in Kubernetes, and I also use Percona Server Exporter tools.

Using Percona Server for deploying MongoDB servers in Kubernetes helps my team day-to-day by allowing us to quickly deploy small replica sets of MongoDB and configure it in YAML files.

I use Percona MongoDB Exporter to export all metrics to Grafana.

Percona Server offers excellent features including being open source, which allows us to use the tools the way we want. Percona Kubernetes for MongoDB is a unique offering since no other companies provide a proper Kubernetes operator that supports deployment, maintenance, and backup.

Percona's unique Kubernetes Operator for MongoDB has made my life easier by first providing backup, which is the main feature for databases, and it also includes advanced maintenance features when I need to upgrade to the next version of MongoDB.

Additionally, Percona has a great community, so I can always expect help from Percona fans regarding the features.

Percona Server has positively impacted my organization because it is open source, and if the official MongoDB goes in different directions or makes its product expensive, we can still use Percona Server, which serves as a sort of safety net.

This safety net has helped my organization save costs, as Percona costs nothing in the community version.

I believe it would be great to have tools to deploy Percona Server in Docker so that we can split a huge database server into many small servers, which are easier to maintain and delegate to junior administrators.

I also think there should be more use cases and documentation on deploying in Kubernetes with real-life examples, as currently, the documentation is minimal, making it difficult in a production situation.

I have been using Percona Server for more than a year.

Percona Server is perfectly stable and reliable.

Percona Server's scalability meets our needs well, as we use it in Docker and scale the way we want with multiple MongoDB servers rather than one huge server, so scalability is in our hands and not Percona's, and it works well for us.

I previously used FerretDB, but I think it is not mature enough, and we also considered CockroachDB.

Before choosing Percona Server, I did not really evaluate other options since developers are conservative people and once they use a NoSQL solution, they prefer MongoDB over all other options.

We have definitely saved money since using Percona Server.

I do not have experience with pricing, setup cost, or licensing for Percona Server.

My advice to others looking into using Percona Server is to learn Linux, Kubernetes, and test Percona Server before running it in production.

I'm in the process of running a POC.

Initially, I've been working on the vendor side and we can only suggest to the vendor how to use Percona Server as opposed to MySQL's community version. I was just working on MySQL Server to see the difference between the community version and this and how the performance goes. I'm doing the R&D on my side.

It's easy to use, and the community is really nice. For example, if I have an issue, I can search for it, and the issue can get solved really quickly. 

There are a lot of benefits. The tools which Percona provides for backup and recovery, like Percona XtraBackup, are great.

The initial setup is simple. 

It's scalable.

We find the product mostly stable.

It's open-source, making it free to use. 

The community surrounding Percona is quite helpful.

I would love to see the flashback in Percona MySQL or even in Percona PostgreSQL. It's available in Oracle, the flashback. 

In Oracle, there's the utility of a flashback. It stores all the information in the tables for a few days. That way, if I accidentally delete my records from the table or I need to check the value of a column or row two days back, I can. If Percona had flashback capabilities, it would be ideal. 

I would love to see training be easier to find. I had some complications finding the training that Percona provides. It is not displayed on the website. For example, if I want to train myself via a Percona expert through virtual files or through recorded videos or something like that, it's really difficult to find any sort of course. You have to email them first, and they will ask you whether it is for yourself or it is for the corporate sector. The course content should just be readily available and not hidden.

I've been using the solution for almost a year.

Overall, it is stable, and I have built multiple sorts of applications in my testing environment. I deliberately bought the database machine and then started it up. So far, it has been really good. Sometimes, however, it does cause an unknown error. For example, it might say some of the files are corrupted or something like this. That's the nature of the OS. When a machine crashes, it does have an impact on the files.

I'd rate the solution's stability eight out of ten overall. 

The solution can scale well. I have not come across any issues. I'd rate the ability to scale ten out of ten.

As compared to the licensed product, where money is money and money can buy you things, there isn't much direct support. That said, I have never found any sort of an issue that could not be found on the community forum or something like that. And I did approach some of the guys from Percona and they provided me with a good knowledge base. I'm also a member of a Percona community. Whenever I raise a question there, there is always someone who can help. It's pretty good. And this all comes with zero costs attached. 

I'm also doing a POC with MySQL.

Percona does also have MySQL and MySQL is also licensed, which is under Oracle. I have not used the enterprise version, however, I have experience with the enterprise version of Oracle where we have the support of Oracle and a licensing program. The difference between open source and licensed databases is the money which can make things easy. 

The setup is straightforward. It's really easy to use. Even a beginner or someone new to reporting for PostgreSQL or MySQL can easily install it on their local virtual machines, and they can play with the databases.

I'd rate the ease of implementation ten out of ten. As compared to Oracle, it's really easy to use and easy to understand as well as deploy.

We deployed on a local environment; if the internet is stable, it will hardly take up to ten minutes to set up on Ubuntu Debian services. I'm not too sure about the OS version of the other Linux versions.

This is an open-source product and is free to use. 

I'm an end-user. 

I'd advise new users to just go slow, step by step, in order to keep things simple. Don't try to jump ahead. If you go slow, you will get used to everything, and soon you'll be learning very quickly.

I'd rate the solution eight out of ten. 

In my use of Percona Server, I've found that the replication and High Availability features are the most valuable.

It doesn't reclaim disk space when rows are deleted. There have been requests for this feature for some time now. The developers say that it's very difficult to do, which I understand, but it's been several years.

I've used it for six years.

I've had no issues with deployment.

I've had no issues with stability.

I've had no issues with scalability.

Because it's open source and free, there's no customer service.

Because it's open source and free, there's no technical support.

This is the only version I've used, which is basically MySQL.

The setup was very straightforward as the documentation and community were very good with guidance.

I implemented and deployed it by myself.

The product is free, so the ROI is high.

It's free.

My general advice, which is for any database really, is to plan ahead and design the database accordingly and, over a period of time, tweak the configurations in the my.cnf file.