whichdb
vs

FiloDB vs VictoriaMetrics

FiloDB: Distributed in-memory time-series database with PromQL, ingesting from Kafka and persisting to Cassandra. VictoriaMetrics: Resource-frugal, Prometheus-compatible metrics database, run as a single binary or a sharded cluster.

key differences

  • Only FiloDB has secondary indexes, columnar storage, in-memory.
  • Only VictoriaMetrics has ttl / expiry.

choose filodb for

  • +Large-scale operational metrics for dashboards and alerting
  • +Long-retention Prometheus-compatible storage at high cardinality
  • +Real-time event and application-metric debugging

best at · Time-series, Observability, Real-time analytics

choose victoriametrics for

  • +Long-term storage for Prometheus metrics
  • +Kubernetes monitoring with vmagent and the operator
  • +Consolidating Graphite, Influx and Prometheus metrics in one store
  • +High-rate IoT telemetry

best at · Observability, Time-series, IoT

FiloDBDistributed in-memory time-series database with PromQL, ingesting from Kafka and persisting to Cassandra.
VictoriaMetricsResource-frugal, Prometheus-compatible metrics database, run as a single binary or a sharded cluster.
overview
Primary model
Time-Series
Time-Series
Also supports
Columnar / OLAP
–
Type
Database engine
Database engine
Status
Active
Active
Developer
FiloDB contributors (started by Evan Chan)
VictoriaMetrics Inc.
First release
2015
2018
Latest version
0.9.17.2 (Nov 18, 2022)
1.155.0 (Oct 26, 2026)
License
Open source (permissive)Apache License 2.0
Open source (permissive)Apache License 2.0
Free tier
✓
✓
popularity
WhichDB Score
2.2
26.8
Rank
#489
#109
GitHub stars
1.5K
17.9K
Stack Overflow questions
–
143
scale & guarantees
Comfortable data size
Large (≤ 1 PB)
Large (≤ 1 PB)
Horizontal scaling
Native
Native
Multi-region
None
None
ACID
None
None
Consistency
Eventual
Eventual
Schema
Flexible
Schemaless
Architecture
Distributed, In memory
Single node, Distributed, Client server
deployment
Self-hosted
✓
✓
Vendor-managed cloud
—
✓
Serverless
—
—
Embedded
—
—
Edge
—
—
Clouds
–
AWS
capabilities
Transactions
—
—
Joins
—
—
Secondary indexes
✓
—
Full-text search
—
—
Vector search
—
—
Geospatial
—
—
JSON
—
—
Change data capture
—
—
Triggers
—
—
Stored procedures
—
—
Materialized views
—
—
TTL / expiry
—
✓
Pub/Sub
—
—
Columnar storage
✓
—
In-memory
✓
—
Durable persistence
✓
✓
Compression
✓
✓
Encryption at rest
—
—
Role-based access
—
—
Time travel
—
—
Branching
—
—
Online schema changes
—
—
Streaming ingest
✓
✓
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
PromQL
MetricsQL, PromQL
Client languages
–
–
Best for
Time-series, Observability, Real-time analytics
Observability, Time-series, IoT
Add more to this comparisonNot sure either fits? Try smart match

FiloDB vs VictoriaMetrics: FAQ

What is the difference between FiloDB and VictoriaMetrics?

FiloDB: Distributed in-memory time-series database with PromQL, ingesting from Kafka and persisting to Cassandra. VictoriaMetrics: Resource-frugal, Prometheus-compatible metrics database, run as a single binary or a sharded cluster. Only FiloDB has secondary indexes, columnar storage, in-memory. Only VictoriaMetrics has ttl / expiry.

When should I choose FiloDB over VictoriaMetrics?

Choose FiloDB for large-scale operational metrics for dashboards and alerting; long-retention Prometheus-compatible storage at high cardinality; and real-time event and application-metric debugging. Choose VictoriaMetrics for long-term storage for Prometheus metrics; kubernetes monitoring with vmagent and the operator; and consolidating Graphite, Influx and Prometheus metrics in one store.

Is FiloDB or VictoriaMetrics more popular?

VictoriaMetrics ranks #109 on the WhichDB Score (26.8/100) and FiloDB ranks #489 (2.2/100). Popularity is not fit: check the requirements that matter for your project.

Are FiloDB and VictoriaMetrics open source?

Yes. FiloDB is open source. License: Apache License 2.0. Yes. VictoriaMetrics is open source. License: Apache License 2.0.