FiloDB vs KairosDB
FiloDB
github.comKairosDB
kairosdb.github.ioSide by side
| Figure | FiloDB | KairosDB |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Time-Series Databases | 8.1 (#12) | 7.3 (#31) |
| Deployment | FiloDB is deployed as standalone processes in a cluster and requires Java, Cassandra, Kafka, Rust, and a C compiler to build; SBT is also listed as a build prerequisite. | The documentation says KairosDB runs under Kubernetes and is mostly stateless, while Cassandra can be harder to run efficiently there. |
| License | The repository identifies Apache-2.0 as its license. | The repository identifies the license as Apache License 2.0. |
| Product | FiloDB is an open-source distributed, real-time, in-memory time-series, event, and operational database with Prometheus query support. | KairosDB is a distributed time-series database built on Cassandra. |
| Support | The repository invites contributions; it does not state a paid support plan on the README page. | The project README directs users to a KairosDB discussion group for questions and community involvement. |
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.
KairosDB
KairosDB has no write-up on Specifiction yet; its figures are above.