Axibase Time Series Database vs FiloDB
Axibase Time Series Database
axibase.comFiloDB
github.comSide by side
| Figure | Axibase Time Series Database | FiloDB |
|---|---|---|
| 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 | 0 | 1 |
| Spec score · Time-Series Databases | 7.6 (#25) | 8.1 (#12) |
| Deployment | ATSD installation package documentation lists Linux distributions including Ubuntu, Debian, RHEL/CentOS, and SLES. | 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. |
| Integrations | Axibase Collector supports data collection jobs for AWS, Docker, HTTP, JDBC, JMX, Kafka, SNMP, and other sources. | The README describes using FiloDB as a Grafana data source through its Prometheus-compatible HTTP API and identifies Cassandra as its persistence store. |
| Querying | ATSD supports SQL for querying and analyzing time series data. | FiloDB supports PromQL through an HTTP API and CLI, and the README says its PromQL support is about 60%. |
| Support | The documentation lists commercial support through its Support Desk and trial-period support by email. | The repository invites contributions; it does not state a paid support plan on the README page. |
Plans
In their own words
Axibase Time Series Database
Axibase Time Series Database has no write-up on Specifiction yet; its figures are above.
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.