

MySQL and InfluxDB are popular databases competing in the database solutions category. MySQL appears to have the upper hand in terms of pricing and support, while InfluxDB stands out for its features and scalability, appealing for specific use cases despite higher costs.
Features: MySQL is known for its multi-threaded architecture, triggers, replication, and full-text search, making it flexible and reliable for small to medium applications and popular in web development. InfluxDB excels in time-series database capabilities, efficient data handling, and strong performance with visualization tools, although it may lack some relational features compared to MySQL.
Room for Improvement: MySQL users highlight challenges with InnoDB complexity, limited support for advanced RDBMS features, and replication reliability. InfluxDB could improve with better clustering, user-friendly interfaces, and comprehensive documentation for easier integration with other tools.
Ease of Deployment and Customer Service: MySQL offers flexibility in deployment across various environments and extensive community support due to its open-source nature. InfluxDB supports diverse deployment options, though users seek better integration. MySQL relies on community forums for support, while InfluxDB users may face higher support costs.
Pricing and ROI: MySQL is cost-effective with a free open-source version and paid enterprise options, offering solid ROI for basic database functions without licensing fees. InfluxDB, also open-source, may incur scaling costs with recent price increases impacting its value for extensive deployments. Both can provide good returns depending on business needs and technical demands.
These improvements translated into both cost savings and better service reliability, directly impacting business outcomes.
It simplifies processes and reduces the need for additional employees.
InfluxDB reduced my time to show data without any interruption, also reducing the number of people needed to manage the project; it is very good to have InfluxDB in my project.
I have seen a return on investment with MySQL, as it allows us to manage with fewer employees, focusing on business logic rather than database management.
They get on a call, resolve issues, and handle everything efficiently.
The InfluxDB support team was knowledgeable and helped us troubleshoot complex problems efficiently.
Obtaining that quantity of data directly from InfluxDB is quite challenging, and that is why we ask for help from the InfluxDB team to retrieve the data to avoid timeouts and those kinds of issues.
I would rate the documentation and online support a 10 out of 10.
We have no issues and usually receive timely responses.
The main challenge with InfluxDB, which is common with all databases, was handling very high throughput systems and high throughput message flow.
It can handle large volumes of time-series data and with high ingestion rates, making it suitable for enterprise-scale deployments.
We’ve scaled on volume with seven years of continuous data without performance degradation.
Meeting scalability requirements through cloud computing is an expensive affair.
MySQL's scalability is currently adequate, as we have increased operations from ten thousand to twelve thousand devices, and it is working fine for us.
It serves as the backbone of our application, and its stability is crucial.
We have used it to support mission-critical systems with continuous data ingestion and real-time analytics.
It is very stable, with no reliability or downtime in InfluxDB.
We face certain integration issues, especially when we integrate the database with security solutions like IBM QRadar.
From my experience, MySQL was pretty stable.
InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying.
Having a SQL abstraction in InfluxDB could be beneficial, making it more accessible for teams that prefer querying with SQL-style syntax.
It could include automated backup and a monitoring solution for InfluxDB or a script developed by a REST API.
It could be more beneficial if MySQL can enhance its data masking functionality in the same way it has improved data encryption.
Oracle could improve on scalability.
The load balancer, MySQL LB, which is used to connect to the application, lacks clear documentation.
We use the open-source version of InfluxDB, so it is free.
I find the cloud version pricing of InfluxDB reasonable, and for the on-premises solution we use in our service, we need to purchase licenses.
Pricing is based on data volume, retention, and features, which really makes it scalable but requires careful planning to avoid unexpected costs.
Oracle has different components, so if you need security, you have to procure a different license, but here everything is inbuilt and it's not costly.
The most important feature for us is low latency, which is crucial in building a high-performance engine for day trading.
InfluxDB’s core functionality is crucial as it allows us to store our data and execute queries with excellent response times.
It helps me maintain my solution easily because it is very reliable, so we didn't face any performance issues or crashes regarding our queries; we can get the results very fast.
With Oracle, we have to buy another solution for encryption and masking, but MySQL supports native encryption, which enhances our return on investment.
The main feature we utilize in MySQL is the view, and I can say that it is the most valuable feature for our needs.
It allows programming, writing stored procedures, creating views, constraints, and triggers easily.
| Product | Mindshare (%) |
|---|---|
| MySQL | 10.5% |
| InfluxDB | 5.0% |
| Other | 84.5% |


| Company Size | Count |
|---|---|
| Small Business | 9 |
| Midsize Enterprise | 4 |
| Large Enterprise | 8 |
| Company Size | Count |
|---|---|
| Small Business | 75 |
| Midsize Enterprise | 33 |
| Large Enterprise | 61 |
InfluxDB offers efficient time series data handling with fast writes, optimized storage, and seamless Grafana integration, making it ideal for high-volume applications like crypto trading and real-time monitoring. Its SQL-like query language and cloud-based options enhance user experience and system scalability.
InfluxDB stands out with its ability to handle high-volume time series data efficiently, thanks to fast data writes and efficient compression. It is highly scalable, providing clustering features for improved performance management. Integration with Grafana enhances visualization, making it easier to analyze complex data through a user-friendly SQL-like query language. Real-time monitoring, historical data access, and proactive alerts enhance system reliability. Its cloud offering simplifies maintenance and operations, making it attractive for users seeking an efficient time series database.
What are the key features of InfluxDB?InfluxDB is applied extensively in industries handling high-volume data needs. For sensor data storage in production environments, it offers reliable performance. Its role in server management metrics and performance monitoring is crucial for maintaining optimal operations. In crypto market data collection, it supports fast-paced trading environments. Industries use it for real-time tracking, like maritime vessel monitoring, leveraging its rapid data handling and visualization capabilities. Its applications also extend to IoT environments, API performance tracking, HVAC systems, and log aggregation, often integrating with Prometheus, Docker, and AWS to enhance system capabilities.
MySQL is an open-source database known for its ease of use and high performance. It offers features like replication and clustering, making it ideal for diverse applications. Its cost-effectiveness and LAMP integration are key advantages for businesses.
MySQL supports a variety of languages and platforms, providing reliable, scalable data management. Its graphical interface and LAMP architecture integration enhance its usability, while community support further strengthens its appeal. Challenges include scalability issues with large databases, lack of advanced clustering, and limited high-availability features. Complex queries may affect performance, and integration can pose difficulties. The outdated interface and insufficient documentation are also concerns, along with replication and backup reliability issues.
What are MySQL's key features?MySQL is widely implemented in industries such as web development, e-commerce, and finance. It's used for managing dynamic websites, powering e-commerce platforms, and supporting financial applications. Its compatibility with PHP and cost-effectiveness make it suitable for CMS platforms like WordPress. With cloud services integration, MySQL is a backend choice for scalable applications in various sectors.
We monitor all Open Source Databases reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.