InfluxDB
A purpose-built time series database from InfluxData, now rebuilt in Rust around SQL and InfluxQL as its primary query languages.
Last updated
What it is
InfluxDB is a time series database built by InfluxData, first released in 2013 and designed specifically for storing and querying timestamped data — metrics, events, sensor readings — rather than being a general-purpose database repurposed for the job. It has gone through several major architectural generations with different storage engines and query languages, which is worth knowing before evaluating it: InfluxDB 1.x used InfluxQL (a SQL-like language), InfluxDB 2.x introduced Flux (a functional scripting language) as its primary language, and the current generation, InfluxDB 3 (built on the Apache Arrow and DataFusion ecosystem and rewritten in Rust), has moved back to SQL and InfluxQL as the supported query languages, with Flux now in maintenance mode for existing 2.x users rather than being carried forward. This is an important detail for anyone starting fresh today: new deployments should plan around SQL/InfluxQL, not Flux.
InfluxDB 3 ships in an open-source edition (InfluxDB 3 Core), a commercially licensed self-managed edition with additional scale and management features (InfluxDB 3 Enterprise), and managed cloud offerings run by InfluxData.
Why teams choose it
- Purpose-built storage and compression for time series data generally outperforms shoehorning the same workload into a general-purpose relational or document database, particularly for high-write-volume sensor and IoT use cases.
- The query language churn across major versions is a genuine adoption risk — teams that built dashboards and alerting around Flux in InfluxDB 2.x face real migration work if they move to InfluxDB 3, since Flux isn’t part of that engine’s future.
- SQL support in InfluxDB 3 lowers the learning curve considerably compared to Flux, and makes the database easier to connect to existing SQL-literate tooling and BI systems.
- Less Kubernetes-native and less of a pull-based ecosystem standard than Prometheus — InfluxDB is push-based and works well for IoT, sensor, and application-metrics use cases outside the cloud-native/Kubernetes world where Prometheus dominates.
Pricing model
InfluxDB 3 Core is free and open-source. InfluxDB 3 Enterprise is commercially licensed for self-managed deployments needing features like read replicas, more granular retention, and enterprise support, generally priced through direct sales. InfluxData also offers managed cloud tiers with a free entry tier and usage-based paid tiers billed on data volume and query load. As with most time series databases, evaluating total cost requires understanding both the licensing model and the underlying compute/storage consumption.
Alternatives
Within the time series database space, Prometheus (paired with VictoriaMetrics or Grafana Mimir for long-term storage) is the dominant alternative for cloud-native and Kubernetes-centric workloads, while TimescaleDB (a PostgreSQL extension) is a common choice for teams wanting SQL and relational features alongside time series data. For managed alternatives that remove operational burden entirely, Datadog and Amazon CloudWatch both offer metrics storage as part of broader platforms.