InfluxDB vs. Percona Server

InfluxDB is a time series database and should be used in that intent. Each data ingestion streams should be properly configured to ensure optimal database performance. InfluxDB works very well but like any other databases requires maintenance and tuning. We have been using the TICK stack and are very happy with the results.

Incentivized

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.

Incentivized

• Time series data
• Very fast queries
• Many options to configure and tune database

Incentivized

• Feature Rich: Percona Server for MySQL always has some additional features on top of MySQL.
• Performance improvements: Additional performance
• Integration with Native and Community tooling: It supports all native and community developed tooling for MySQL

• Small, but growing community - This database engine's community is much smaller than alternatives. This can make finding a DBA or support less easy, but not impossible.
• Documentation could be improved - The docs for getting started don't effectively lead first-time users to understand how the underlying systems are designed.
• Performance Analysis - There seems to be a lack of tools to give context to slow queries or other performance issues
• Out-of-the-box security - The out of the box security is designed to operate in an internal network and is limited.

Incentivized

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

InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.

Incentivized

Good community support.

We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.

Incentivized

We are using opensource so we have not used customer support.

We have looked around to find different options we had when we first started to move to cloud. At that time, the options we had is Google Cloud BigTable and InfluxDB. But quickly we realized that InfluxDB is the database specialized in time series database and performs better than other options we have.

Incentivized

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

• Provided us a time series DB.
• With the SQL-like language, it is very easy to learn.
• Empowered us to keep track of our events.

Incentivized

• Increased efficiency with faster querying
• Easy scalability