TrustRadius Insights for InfluxDB are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
High Availability and Scalability: Many users appreciate the high availability and scalability of InfluxDB, making it suitable for handling large amounts of data. Several reviewers have mentioned that they can rely on InfluxDB to efficiently handle their data needs, allowing them to scale their applications without worrying about performance issues.
Real-time Performance: The real-time performance of InfluxDB is impressive, with fast query execution times and low latency. Numerous users have praised its ability to provide quick insights and analysis on real-time data. This makes it an ideal choice for tasks such as real-time monitoring and data analysis.
Ease of Use in Querying and Processing Data: Users find one of the key strengths of InfluxDB lies in its ease of use when querying, filtering, and processing data. They appreciate the built-in data explorer, dashboard building capabilities, and alert mechanisms that simplify these tasks. Several reviewers have expressed their satisfaction with how intuitive it is to work with InfluxDB's interface for data manipulation.
InfluxDB is being used by some department of our company as a time-series database. We use that to monitor the infrastructure we have on cloud and InfluxDB is also hosted on cloud server. Once there is an event triggered, the event will be stored in InfluxDB for future reference use.
Pros
Perfect handling telemetry data.
Low latency, near real time.
SQL-like language makes it easier to query.
Cons
Query return can sometime out of order.
Some operations can be hard to execute, like delete function.
Have to be aware of timely order to have a good performance.
Likelihood to Recommend
One part of our event-driven architecture on cloud is to implement real-time event logging. We have looked into different products on the market and found InfluxDB being the perfect balance between cost and efficiency. We had a small size proof of concept and decided that was what we wanted to go with. And so far it is working great with our other components on cloud.
VU
Verified User
Engineer in Information Technology (10,001+ employees)
InfluxDB is being used by our IT teams in conjunction with other products (Grafana, Kafka, Chronograf). This allows us to analyze and troubleshoot issues based on metrics collected across our IT infrastructure within InfluxDB. So far, InfluxDB is performing extremely well in terms of data indigestion and query speeds. We will continue using this software as it absolutely meets our requirements.
Pros
Time series data
Very fast queries
Many options to configure and tune database
Cons
GUI based administrator console
Likelihood to Recommend
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.
We use InfluxDB to provide a performant and scalable time series database for business intelligence, system statistics, and customer usage. InfluxDB allows us to effectively throw as much data as we can at the database while reducing it into usable and performant data when accessed. Our relatively small team of engineers was able to research and implement the database setup and implement a working data input model into our application in a short two weeks.
Pros
Scalability - InfluxDB scales so well and even lets you create a database cluster without needing a database administrator.
Data Reduction - InfluxDB's primary use case is to allow the data to be input at any interval or speed regardless of the volume of data. The way this is later queried is by reducing the data based on the input data.
Quick start - Unlike other monolithic time series database it can easiliy startup with just a few minutes of reading their documentation
Cloud Native - This database engine is made to operate in Docker & cloud first!
Cons
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.
Likelihood to Recommend
InfluxDB is the perfect database for stats or other time-based data that would overwhelm SQL or NoSQL databases. This makes reporting, graphs, and other parts of your application simple to implement. The multitude of functions to allow data to be analyzed and reduced makes this a very powerful database engine.
I would NOT recommend InfluxDB for any non-time-based data.
As a Consultant, I often choose InfluxDB as a time-series database for my customers when they need to store metrics from their monitoring systems. Since InfluxDB is widely spread, many other software products offer some sort of integration (such as Grafana). Therefore, metrics graphs based on InfluxDB data are often embedded into other software products which are being used by my customers.
This solves the problem that customers often have to get used to different graphical interfaces when viewing common monitoring data and performance metrics. But since graphs (based on InfluxDB data) can get embedded into main GUIs, customers only need to login into one interface and have a complete overview of their data.
InfluxDB itself solves another problem. In the past, many companies used MySQL-like products to store time-series data. This was highly inefficient and difficult to manage. With InfluxDB, many issues those customers had disappeared.
Pros
Storing time-series data
Providing time-series data over an HTTPS API
Accepting new data inputs through the same HTTPS API
Providing existing data sets in a very fast and efficient manner
Cons
The open source version does not have ACLs, which is crucial for enterprise customers
The open source version has no high availability or clustering option, even the enterprise edition is limited in this way
The open source and the enterprise versions both have no read load-balancing systems (sharding is possible, though)
Backup and recovery can only be performed for all data sets, not for subsets
Likelihood to Recommend
InfluxDB is very good at storing monitoring metrics (e.g. performance data). InfluxDB is not the right choice if you need to store other data types (like plain text, data relations etc.).