No more typing reviews! Try our Samantha, our new voice AI agent.

InfluxDB vs ScyllaDB comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 7, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

InfluxDB
Ranking in NoSQL Databases
6th
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
20
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), Network Monitoring Software (14th), IT Infrastructure Monitoring (12th)
ScyllaDB
Ranking in NoSQL Databases
8th
Average Rating
7.8
Reviews Sentiment
7.0
Number of Reviews
12
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of September 2026, in the NoSQL Databases category, the mindshare of InfluxDB is 5.1%, down from 6.9% compared to the previous year. The mindshare of ScyllaDB is 5.7%, down from 9.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
InfluxDB5.1%
ScyllaDB5.7%
Other89.2%
NoSQL Databases
 

Featured Reviews

Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at Energybox
Time series data has been managed efficiently for IoT sensors but reporting still needs improvement
How InfluxDB can be improved is relevant since for Energy Box, we face certain issues. We have customers worldwide, including the United States, United Kingdom, and Europe, but when we expanded to China two years ago, they indicated that they do not support the cloud version there. Our application is built on the cloud, which required us to create a separate application for Azure China, which was painful for us. The second issue involves frequent version changes. For example, we started with version one, transitioned to version two, and I heard they are considering InfluxDB version three, reverting to earlier practices. InfluxDB should improve without completely changing its approach. Now we have to redo our work for InfluxDB version three. Regarding needed improvements, the documentation is sufficient, but pricing presents a challenge. InfluxDB has standard pricing, which is acceptable for large companies. However, for startups in our position, they should provide special discounts so everyone can utilize it. The pricing should adapt as companies grow, which is a reasonable expectation.
Manikandan Gunasekaran - PeerSpot reviewer
Director of Engineering at Ola
Reliable data management with great reliability and performance
From a sales pitch standpoint, it needs to deliver on promises of better ROI and compaction. Additionally, ticketing and support systems could be improved due to the time it takes to get answers. There's also an issue with compatibility when attempting to switch back from the enterprise to the community version.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Prior to InfluxDB usage, real-time data was not visualized and monitored, and after the introduction of InfluxDB in the entire framework, the organization is benefiting a lot in terms of monitoring and understanding performance data in real-time."
"InfluxDB positively impacts my organization because I have optimized my database storage, and by using powerful queries, I am able to find my data logs efficiently and also manage logging."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"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."
"While I would rate InfluxDB a ten on a scale of one to ten, users should be thoughtful about matching the engine to their specific needs."
"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."
"The performance and scalability are good, and we hardly see any major issues with ScyllaDB."
"ScyllaDB allows fine-tuning of the table structure. Speed is probably the most critical factor because we perform a lot of heavy data ingestion. One of its core features is its ability to handle high volumes and maintain speed when accessing data. Additionally, high availability and partitioning are built-in features of ScyllaDB."
"The best features of ScyllaDB are how it synchronizes data and its failover system. There's a unique formula to decide the number of nodes you need and the minimum required, which I find helpful. It also offers encryption and supports APIs, making it great for distributed systems and scaling databases across different regions. While it's easy to use, having prior experience helps configure it properly. There are many configurations; if you don't understand them, you might mess up the design. So, understanding your system's needs, like whether it requires more read or write operations, is crucial for setting up the correct configuration."
"Firstly, if I update something, it's most likely to finish within milliseconds."
"The performance aspects of Scylla are good, as always... A good point about Scylla is that it can be used extensively."
"It is lightweight, and it requires less infrastructure."
"The documentation is good. It integrates easily with our existing data infrastructure."
"ScyllaDB is fast and reliable. It has good performance."
 

Cons

"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"The error logging capability can be improved because the logs are not very informative."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
"InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times."
"I chose an 8 out of 10 because there is room for improvement, such as regarding backups and enhanced security through other types of authentication or encrypted data in TLS."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
"The solution's UI can be more user-friendly."
"If you don't have the best computing resources, then it's not easy to set up. In such cases, we have to run ScyllaDB in developer mode."
"The product needs to add more features and improve the response time of the support team."
"The documentation is not well established for new developers."
"Some of the regular commands in NoSQL do not work."
"We faced several challenges while integrating ScyllaDB into our AWS environment. One common issue was that a security port wasn’t opened on one node, preventingdata synchronization across clusters. We noticed the data wasn’t syncing correctly when we saw different record counts in other regions. After investigating, we found that the port was closed in one AWS region. Once we opened the port, the data synchronization across all nodes resumed as expected."
"From a sales pitch standpoint, it needs to deliver on promises of better ROI and compaction."
"It seems we have better options available. So probably don't go for ScyllaDB. The reason is, first, it's very high. It's not as straightforward as, like, Postgres or ClickHouse to set up. It requires a complex setup."
"ScyllaDB needs to improve its handling of transactions."
 

Pricing and Cost Advice

"The tool is an open-source product."
"InfluxDB is open-source, but there are additional costs for scaling."
"We are using the open-source version of InfluxDB."
"The paid version of ScyllaDB is not that expensive. The main advantage of the paid version is direct support from the ScyllaDB team, which can resolve issues faster—typically within a day, compared to two to three days with the free version. The paid version also offers better guidance and support, while the free version has good documentation and is more high-level. I’d rate their support team nine out of ten because of the quick responses from their community."
"It's a bit expensive."
"It's free."
"It is an expensive tool compared to its competitor."
"I believe that there is a yearly licensing cost and that it's expensive."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
11%
Financial Services Firm
10%
Manufacturing Company
10%
Construction Company
9%
Outsourcing Company
15%
Comms Service Provider
9%
Financial Services Firm
8%
Transportation Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise5
Large Enterprise9
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise2
Large Enterprise8
 

Questions from the Community

What needs improvement with InfluxDB?
If the dashboarding facility can be improved in terms of the visualization parameters and the amount of support available from the community, as well as having smarter alerts to send those alerts t...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is to inject all my performance data and visualize it as a data source into Grafana. My data comes from JMeter from a plugin, which is inserting data to InfluxDB, and ...
What advice do you have for others considering InfluxDB?
It is good to start with InfluxDB to stabilize your data, visualize your data, and have the data stored on a time-series basis. I would recommend everyone to get into InfluxDB and start using it. T...
What is your experience regarding pricing and costs for Scylla?
From what I’ve seen (and experienced), ScyllaDB pricing is very dependent on how you deploy it, and that’s where most of the confusion comes from.
What needs improvement with Scylla?
From a sales pitch standpoint, it needs to deliver on promises of better ROI and compaction. Additionally, ticketing and support systems could be improved due to the time it takes to get answers. T...
What is your primary use case for Scylla?
We dump a lot of our data, such as every entry created with respect to when a user rides a scooter, every record gets updated to ScyllaDB. It is used as a single source of truth and it manages mass...
 

Comparisons

 

Overview

 

Sample Customers

ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
IBM, Investing.com, mParticle, Comcast, GE, Fanatics, Ola, CERN, adgear, Samsung
Find out what your peers are saying about InfluxDB vs. ScyllaDB and other solutions. Updated: September 2026.
913,806 professionals have used our research since 2012.