Perfect for storing time-series data
Rating: 10 out of 10
IncentivizedUse Cases and Deployment Scope
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.
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.).
