QuestDB vs. VictoriaMetrics Community

QuestDB is well suited for any use case where you need to store large amount of data and the performance is the key factor - for both reads and writes. So use cases like market data storage in financial industry, any kind of telemetry, etc.

1. It is well suited when you need to monitor large scale of metrics as compared to Prometheus it is faster,more reliable and can provide you metric for more retention period. 2. Uses less resource to run application , can easily be containerised 3. It supports both push and pull models and can be intergated with multiple alerting systems

Incentivized

• Extreme performance.
• Super easy to use.
• Compatibility with Influx line protocol.
• PostgreSQL compatibility.
• Out of order timestamps.
• Support for multiple records with same timestamp.
• Integration with Grafana.
• Team responsiveness.

• Easy to configure and manage
• Ready to be configured at cloud and microservices
• Easy to scale vertically and horizontally

Incentivized

• New project so needs a bit polishing.

• Community and Eco system -> Although it supports the ecosystem of Prometheus, it is still troublesome for someone who's not using Prometheus
• Configuration is not so easy, especially if you are a beginner, you will struggle a bit. Even the documentation is not so welcoming for beginners
• Built-in Visualisation is bare minimal, leading almost everyone to use some other extension/tool

Incentivized

We were looking for time series database that will be able to handle L2 market data and came across QuestDB. From the beginning we were impressed how well the QuestDB performs and that it actually significantly outperforms all other open source TSDB on market like InfluxDB, ClickHouse, Timescale, etc. Apart from the excellent performance it is also super easy to use and deploy which makes the experience of using the database very pleasant - we were able to be up and running and storing data within few hours. Topic itself is the QuestDB team that is super responsive on their slack channel and always ready to help with any query. They are constantly improving the product and if there is some missing feature that is blocking you from usage they always try the best to implement such feature asap and release a new version - one of the best support I have ever seen so far in open source community.

Victoria metrics is cheaper and more efficient than Prometheus, in terms of data ingestions, hardware resources, and Storage mechanism, also supports Prometheus extensions, and query language by default. Although Prometheus has a larger community and support, because of the interoperability of Victoria metrics the difference wouldn't concern us much. At the same time, it made our migration simpler

Incentivized

• Reduced cost.
• Increased efficiency.
• Faster time to market.

• Lowered our infra costs in comparison with our older tools
• Need minimal effort for migration since it already supports Prometheus ecosystem
• Saved on Storage costs

Incentivized