FiloDB vs Netflix Atlas
FiloDB
github.comNetflix Atlas
netflix.github.ioSide by side
| Figure | FiloDB | Netflix Atlas |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Time-Series Databases | 8.1 (#12) | 7.1 (#32) |
| 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 overview says Netflix wanted common query capability for third-party services such as CloudWatch. |
| License | The repository identifies Apache-2.0 as its license. | The repository states that Atlas is licensed under the Apache License, Version 2.0. |
| Scale | It is designed to ingest and query many millions of time series, with data sharded across processes and distributed querying built in. | Atlas was designed to scale with the hardware used to analyze and store its data. |
| Storage | Columnar compression and off-heap memory management help it store substantial data in memory while reducing garbage collection. | Atlas uses in-memory data storage to gather and report very large numbers of metrics quickly. |
| Support | The repository invites contributions; it does not state a paid support plan on the README page. | The repository links to a mailing list and GitHub issues for community contact and issue reporting. |
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.
Netflix Atlas
Netflix Atlas has no write-up on Specifiction yet; its figures are above.