When comparing Timescaledb vs VictoriaMetrics, the Slant community recommends Timescaledb for most people. In the question“What are the best time-series databases and/or data stores?” Timescaledb is ranked 1st while VictoriaMetrics is ranked 4th. The most important reason people chose Timescaledb is:
Implemented as a PostgreSQL extension, not a fork.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Powered by PostgreSQL
Implemented as a PostgreSQL extension, not a fork.
Pro Reliable at its core
Based on PostgreSQL hence inherits PostgreSQL’s operational maturity.
Pro Highly available
Support for streaming data replication and robust backup / recovery.
Pro Enterprise-grade security
Fine-grained access control, LDAP support, encryption, and flexible authentication built-in.
Pro Handle high query traffic
Deploy read replicas for higher query throughput.
Pro Data lifecycle management
Support for efficient data retention and archiving.
Pro Data model freedom
Store schemas or go schema-less with JSON. Use narrow or wide tables. Stop worrying about high cardinality.
Pro Geospatial queries
Grow your use case with PostGIS.
Pro Fast and cost-effective
VictoriaMetrics requires fewer hardware resources - RAM, CPU, storage - compared to competitors. This allows for saving hardware costs.
Pro Easy to setup and operate
Just start a single binary with the minimum amount of settings.
Pro Different protocols support
Supports metrics' scraping, ingestion and backfilling via the different protocols - see here.
Pro Seamless integration with Prometheus+Grafana
Prometheus may be configured to write data to VictoriaMetrics. Grafana may be configured to query the data directly from VictoriaMetrics using PromQL.
Pro Open source
VictoriaMetrics is free and open source - see here.
Pro Cluster version is free and open source
Cons
Con Built from scratch
It is young and it is built from scratch. This means it can contain unpolished code.
Con Doesn't support SQL
It supports only PromQL for querying data.
Alternative Products
