FiloDB vs UnitDB
FiloDB
github.comUnitDB
github.comSide by side
| Figure | FiloDB | UnitDB |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Time-Series Databases | 8.1 (#12) | 6.9 (#34) |
| 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 maker lists supported Go and Flutter/Dart client libraries for connecting to a UnitDB server. |
| License | The repository identifies Apache-2.0 as its license. | The repository states that UnitDB is licensed under Apache-2.0. |
| Product | FiloDB is an open-source distributed, real-time, in-memory time-series, event, and operational database with Prometheus query support. | UnitDB is an open-source time-series database and publish-subscribe messaging server aimed at IoT and real-time connected devices. |
| Querying | FiloDB supports PromQL through an HTTP API and CLI, and the README says its PromQL support is about 60%. | Its UQL query language supports topic patterns, JSON payload field selection and filtering, grouping, counts, indexes, and deletion by ID or age. |
| Storage | Columnar compression and off-heap memory management help it store substantial data in memory while reducing garbage collection. | The engine supports larger-than-memory data sets, fast lookups and writes, TTLs on message entries, and immutable database opening. |
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.