

MySQL and VictoriaMetrics compete in database and time-series data storage respectively. VictoriaMetrics appears to have the advantage due to its scalability and advanced data processing capabilities.
Features: MySQL offers relational database capabilities, structured query language support, and an extensive ecosystem ideal for complex transactions. VictoriaMetrics provides high performance in time-series data processing, efficient data ingestion, and storage, appealing to those prioritizing speed and scalability.
Ease of Deployment and Customer Service: MySQL provides a traditional deployment model with strong support, suiting organizations in need of reliable technical assistance. VictoriaMetrics offers flexibility with quick deployment capabilities, requiring less configuration time, making it preferable for rapid scaling and ease of integration.
Pricing and ROI: MySQL presents cost-effective initial setup options and strong ROI through low operational costs in structured data environments. VictoriaMetrics, while having higher initial costs due to specialization, can yield substantial ROI in handling large volumes of time-series data, offering value in specialized settings where data speed and volume are crucial.
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.
I have seen a return on investment with VictoriaMetrics, saving 40% in storage costs compared to Prometheus, reducing query latency by 60%, and cutting maintenance time by half.
time was saved due to simplicity and a shorter learning curve compared to other tools.
Because VictoriaMetrics runs more efficiently and much faster, debugging an issue or understanding system performance is much easier.
I would rate the documentation and online support a 10 out of 10.
We have no issues and usually receive timely responses.
We reached out once or twice for minor issues during the initial setup and integration, and they were helpful in resolving the issues.
VictoriaMetrics customer support is exceptional.
We use the open-source version of VictoriaMetrics, so we did not require any customer support.
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 handles large volumes of time series data efficiently, using less memory and disk compared to Prometheus or Thanos.
We deploy and embed it in our Helm chart and it works out of the box.
VictoriaMetrics has handled increases in data and users smoothly so far.
We face certain integration issues, especially when we integrate the database with security solutions like IBM QRadar.
From my experience, MySQL was pretty stable.
In terms of accuracy and reliability, VictoriaMetrics's output is pretty sufficient and works very well in a native Kubernetes setup, which I appreciate.
The components are simple, restarts are fast, and stateless parts can be replaced without data loss.
Regarding stability, I would rate it a ten out of ten.
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.
For our use cases, it is a really good offering, and while we would be interested to see what else it brings in the future, at this point in time it checks all our boxes and we are quite satisfied with it.
VictoriaMetrics is quite a good project and quite easy to use overall.
I compared it with my experience on other time series databases, and it has a huge advantage, so I do not see the need for urgent improvements or optimizations.
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.
We did not require any license for VictoriaMetrics since we are using the open-source version.
I used the free open-source version, and it was sufficient for my needs.
My experience with pricing, setup cost, and licensing for VictoriaMetrics is positive since it is open-source under Apache 2.0, so there is no licensing cost.
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.
MySQL contributes to improved system reliability, faster application performance, and higher developer productivity.
The best aspect of using VictoriaMetrics is the reduction in resources including RAM, memory, disk, and other infrastructure requirements, which have all decreased substantially after implementation.
In my experience, the best features VictoriaMetrics offers include that VM agent does its work very efficiently and does not use a lot of resources.
Its compact storage and fast query performance make it ideal for long-term metric storage.
| Product | Mindshare (%) |
|---|---|
| MySQL | 12.7% |
| VictoriaMetrics | 2.0% |
| Other | 85.3% |

| Company Size | Count |
|---|---|
| Small Business | 75 |
| Midsize Enterprise | 34 |
| Large Enterprise | 64 |
| Company Size | Count |
|---|---|
| Small Business | 3 |
| Midsize Enterprise | 2 |
| Large Enterprise | 2 |
MySQL offers reliability, performance, and cross-platform compatibility, making it a preferred choice for backend applications. Its open-source nature and cost-effectiveness, coupled with strong community support, enhance its appeal for developers.
MySQL, known for its ease of use, is ideal for transactional databases, data management, and analytics. Its support for CRUD operations and ACID compliance ensures data consistency. Features like indexing optimize large queries, while replication boosts scalability. Despite its strengths, users express concerns about performance and scalability under large loads, along with the desire for improved clustering, backup capabilities, and modern tool integration. Enhancing the interface and expanding documentation can elevate the user experience.
What are the main features of MySQL?MySQL finds its place in web and ERP systems, supporting applications in e-commerce, financial services, education, and business intelligence. Its integration with microservices and cloud platforms enables efficient data management, making it suitable for customer management and transactional records in dynamic industries.
Teams that switch to VictoriaMetrics report 70% less RAM and 75% less disk (verified PeerSpot user reviews), and cloud bills up to 10x lower (Grammarly case study) — while keeping their existing dashboards and alerting rules working. It is an open source observability solution for metrics, logs, and traces: a drop-in replacement for Prometheus and other backends that keeps scaling when data volume, query speed, or cost no longer does. It runs anywhere — from a Raspberry Pi to thousand-core clusters, on-premises or in the cloud — and is Kubernetes- and OpenTelemetry-compatible. Built by engineers, for engineers: Over 1B Docker pulls, 19M GitHub downloads, and 27K+ GitHub stars. Simple, reliable, and efficient observability for everyone.
VictoriaMetrics delivers observability in two complementary forms. The open source products are complete, production-grade, and free to run at any scale. Enterprise builds on that same code with capabilities and support for the most demanding environments — it extends open source rather than gating it.
Open source. VictoriaMetrics is a high-performance time series database and monitoring solution, compatible with PromQL via MetricsQL, so existing Prometheus dashboards, recording rules, and alerting rules keep working. VictoriaLogs is a logs database for mission-critical logging, and VictoriaTraces stores and queries distributed tracing data. All three are engineered for minimal RAM, disk, and compute at high ingestion rates.
Enterprise. VictoriaMetrics Enterprise adds features for large, multi-team deployments — plus direct support from the engineers who build the product, with architectural and security guidance. VictoriaMetrics Cloud is the same solution fully managed, and VictoriaMetrics Anomaly Detection applies machine learning to cut alert noise, so the alerts that do reach your team in Slack or on their phones are the ones that matter.
Measured results from users. PeerSpot reviewers report roughly 70% lower RAM use, 75% lower disk use, 3x faster writes, and 7x faster p95 query latency after replacing Prometheus. Grammarly cut its monitoring-related AWS bill about 10x; Granulate reduced metrics storage costs about 5x after moving from Grafana Cloud (Mimir).
Why teams choose VictoriaMetric
What are the key features of VictoriaMetrics?
What benefits and ROI should users expect?
Top use cases
VictoriaMetrics runs in production across finance, telecommunications, energy, scientific research, and IoT — from CERN's particle physics experiments to IHI Terrasun's utility-scale battery storage to Grammarly's product infrastructure. Wherever real-time telemetry at scale is critical, it delivers simple, reliable, and efficient observability for everyone. By engineers, for engineers.
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.