Choose it for a mature TSDB with InfluxQL/Flux when you don't need IoTDB's TsFile or edge-cloud sync.
Scalable datastore for metrics, events, and real-time analytics
- 31.7k
- Rust
- Apache-2.0
time-series database / IoT data management
Apache IoTDB is a Java-based time-series database for industrial IoT, using a columnar file format and SQL-like querying.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
Choose it for a mature TSDB with InfluxQL/Flux when you don't need IoTDB's TsFile or edge-cloud sync.
Scalable datastore for metrics, events, and real-time analytics
Choose it when you want a Java TSDB with SQL and low-latency ingestion but can trade away IoTDB's industrial edge features.
QuestDB is a high performance, open-source, time-series database
Choose it for a Go-based distributed TSDB when you prefer Go over Java and can forgo IoTDB's Hadoop/Spark integration.
LinDB is a scalable, high performance, high availability distributed time series database.
Choose it for Industrial IoT workloads with SQL when you can accept AGPL-3.0 instead of Apache-2.0.
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Choose it for pull-based monitoring with PromQL when you don't need SQL or industrial IoT device management.
The Prometheus monitoring system and time series database.
Choose it for low-cost Prometheus-compatible metrics storage when your workload is monitoring rather than general time-series analytics.
VictoriaMetrics: fast, cost-effective monitoring solution and time series database
Choose it for cloud-native observability on object storage when you need metrics/logs/traces in one engine instead of IoTDB's industrial focus.
The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage.
Choose it when you already run PostgreSQL and want time-series as an extension rather than a separate TSDB.
A time-series database for high-performance real-time analytics packaged as a Postgres extension
These projects were analysed and named iotdb among their alternatives. The relationship is not symmetric — how iotdb rates them is a separate judgement, made when iotdb is analysed in its own right.
calls iotdb “Choose if you want an Apache-licensed TSDB from the Apache ecosystem with an IoT-optimized data model and cluster support.”
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
calls iotdb “Choose Apache IoTDB when you need an IoT-native time-series database with hierarchical schema and embedded deployment options.”
A time-series database for high-performance real-time analytics packaged as a Postgres extension
calls iotdb “IoT/edge time-series DB; choose it for industrial data collection, not a unified observability engine.”
The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage.