apache/iotdbGitHub
calls lindb “Choose it for a Go-based distributed TSDB when you prefer Go over Java and can forgo IoTDB's Hadoop/Spark integration.”
Apache IoTDB
6.4kJavaactive
lindb/lindb Alternatives
lindb is queued for analysis. Crawling candidates and ranking them takes a few minutes. This page updates itself when the list exists — you can also come back later.
What is known so far comes from the other direction:
Listed as an alternative to
These projects were analysed and named lindb among their alternatives. The relationship is not symmetric — how lindb rates them is a separate judgement, made when lindb is analysed in its own right.
influxdata/influxdbGitHub
calls lindb “When you need a horizontally scalable, HA time-series database in Go with low operational overhead and no external dependencies.”
Scalable datastore for metrics, events, and real-time analytics
31.7kRustactive
taosdata/TDengineGitHub
calls lindb “Choose if you want a distributed TSDB focused on metrics with low latency and lightweight query language, not full SQL.”
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
25.1kCactive
timescale/timescaledbGitHub
calls lindb “Choose LinDB when you need a lightweight, distributed TSDB tailored to large-scale monitoring workloads.”
A time-series database for high-performance real-time analytics packaged as a Postgres extension
23.5kCactive
VictoriaMetrics/VictoriaMetricsGitHub
calls lindb “Choose when you need a Kubernetes-native distributed time-series database for metrics and are willing to standardize on its operational model and not necessarily the Prometheus query API.”
VictoriaMetrics: fast, cost-effective monitoring solution and time series database
17.6kGoactive
GreptimeTeam/greptimedbGitHub
calls lindb “metrics-only distributed time-series DB in Go; choose it for a simpler metrics backend if you don't need logs/traces.”
The open-source observability database. One columnar engine for metrics, logs, and traces, on object storage.
6.6kRustactive