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

InfluxDB vs ScyllaDB comparison

 

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 (6th), Network Monitoring Software (14th), IT Infrastructure Monitoring (12th)
ScyllaDB
Ranking in NoSQL Databases
7th
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 August 2026, in the NoSQL Databases category, the mindshare of InfluxDB is 5.2%, down from 7.6% compared to the previous year. The mindshare of ScyllaDB is 5.9%, down from 10.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
NoSQL Databases Mindshare Distribution
ProductMindshare (%)
InfluxDB5.2%
ScyllaDB5.9%
Other88.9%
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

"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 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."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data from servers. It must be installed on Windows or Linux servers. During installation, ensure that the configuration file is correct to prevent issues. Once data is collected, it can be sent to InfluxDB. For visualization, you can use open-source tools like Grafana."
"I recommend going with the cloud version of InfluxDB, as it's very cheap and effective."
"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."
"InfluxDB has played a key role in enhancing system reliability and supporting our goal of delivering a seamless, high-quality product."
"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."
"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."
"ScyllaDB is very fast, and I can use it for so many things."
"The product's most valuable features are efficiency and reliability."
"Scalability in performance is good."
"I like how fast it is to query data from the ScyllaDB node!"
"It is lightweight, and it requires less infrastructure."
"The documentation is good. It integrates easily with our existing data infrastructure."
"The performance and scalability are good, and we hardly see any major issues with ScyllaDB."
 

Cons

"The interface of InfluxDB is so complex and should be made easier for non-technical people."
"However, I cannot ignore the challenges I faced while configuring the database with my message brokers, whether Rabbit or Kafka, because the documentation is not properly provided."
"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."
"If it gets a little bit more into the metric side, then it would really be great, similar to Prometheus."
"I haven't seen a return on investment; unfortunately, I cannot share relevant metrics such as time saved, fewer employees needed, or money saved."
"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
"InfluxDB can be improved by addressing issues such as performance drops, queries being more difficult to understand, and its high memory usage."
"Sometimes, when we write too much data within a minute, the data count becomes excessive, reaching perhaps 100,000 or 500,000 data points, and InfluxDB gives a timeout exception, which we must handle in our application."
"The documentation of Scylla is an area with shortcomings and needs to be improved."
"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."
"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."
"The documentation is not well established for new developers."
"Some of the regular commands in NoSQL do not work."
"We've had occasional performance challenges that required resource adjustments or optimizations in our interaction with the platform."
"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."
 

Pricing and Cost Advice

"InfluxDB is open-source, but there are additional costs for scaling."
"The tool is an open-source product."
"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."
"I believe that there is a yearly licensing cost and that it's expensive."
"It is an expensive tool compared to its competitor."
"It's free."
report
Use our free recommendation engine to learn which NoSQL Databases solutions are best for your needs.
908,834 professionals have used our research since 2012.
 

Top Industries

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

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: June 2026.
908,834 professionals have used our research since 2012.