FiloDB vs TimeBase
FiloDB
github.com
TimeBase
timebase.infoSide by side
| Figure | FiloDB | TimeBase |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | Yes | — |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 2 |
| Spec score · Time-Series Databases | 8.1 (#12) | 7.5 (#28) |
| 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 Community Edition quick start instructs users to run TimeBase in a Docker container and says an installer is also available. |
| 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 connectors for ClickHouse, Timescale, S3, Kafka, and Grafana. |
| Product | FiloDB is an open-source distributed, real-time, in-memory time-series, event, and operational database with Prometheus query support. | TimeBase is an event-oriented, high-performance time-series database and messaging middleware with roots in financial markets. |
| Use cases | Documented uses include operational metrics, distributed tracing storage, ad-hoc application-metric debugging, and real-time event storage and querying. | The maker lists financial markets, IoT, instant payments, and technology health monitoring as use cases. |
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.