FiloDB vs OpenTSDB
FiloDB
github.comOpenTSDB
opentsdb.netSide by side
| Figure | FiloDB | OpenTSDB |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Time-Series Databases | 8.1 (#12) | 7.6 (#26) |
| Integrations | The README describes using FiloDB as a Grafana data source through its Prometheus-compatible HTTP API and identifies Cassandra as its persistence store. | The docs say open-source tools including Grafana and Bosun can access OpenTSDB data. |
| License | The repository identifies Apache-2.0 as its license. | The FAQ says OpenTSDB uses the GNU LGPL v2.1 or later. |
| Querying | FiloDB supports PromQL through an HTTP API and CLI, and the README says its PromQL support is about 60%. | Data can be queried with CLI tools or an HTTP API and viewed as a GnuPlot graph. |
| Scale | It is designed to ingest and query many millions of time series, with data sharded across processes and distributed querying built in. | The homepage says OpenTSDB runs on Hadoop and HBase, scales by adding nodes, and can scale to millions of writes per second. |
| Storage | Columnar compression and off-heap memory management help it store substantial data in memory while reducing garbage collection. | The homepage says data is stored as provided, supports millisecond precision, and can be kept indefinitely. |
Plans
In their own words
FiloDB
FiloDB is a free, Apache-2.0 open-source database for distributed, real-time time-series, event, and operational data. It is designed to ingest and query many millions of time series, sharding data across processes with distributed querying. Columnar compression and off-heap memory management support substantial in-memory storage while reducing garbage collection. PromQL is available through an HTTP API and command-line interface; the README describes support as about 60%. Histograms are a first-class column type, with the project reporting possible compression and query-speed improvements of up to two orders of magnitude. Typical ingestion uses Apache Kafka, while the Gateway accepts Influx Line Protocol over TCP. Grafana can connect through the Prometheus-compatible API, and Cassandra is identified as the persistence store. Deployment uses clustered standalone processes and requires Java, Cassandra, Kafka, Rust, a C compiler, and SBT to build.