FiloDB vs QuestDB

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.

QuestDB is a time-series database for environments where low latency matters, including mission-critical workloads. It supports standard SQL through a vectorized execution engine, along with time-series extensions such as SAMPLE BY, ASOF, and HORIZON JOIN. QuestDB advertises ingestion speeds of 8M+ rows per second. The Open Source edition is self-managed and available as binaries, containers, or source code; it is single-instance and supports Parquet storage and PostgreSQL Wire Protocol compatibility. Ingestion options include QuestDB Wire Protocol, InfluxDB Line Protocol, REST API, native client libraries, SQL INSERT, Kafka connector, and CSV import. Listed integrations include Grafana, Power BI, Apache Kafka, Telegraf, Redpanda, Apache Flink, Pandas, and Apache Spark. Open Source costs nothing and includes community support. Enterprise adds security controls, replication, automatic failover, object-storage tables, and dedicated support with response-time SLAs.