G2

Ajay P.

Senior Manager

Enterprise (> 1000 emp.)

9/19/2023

"Game changer in Time Series Databases"

5/5

What do you like best about QuestDB?

At my organization, we needed to build a real-time analytics system for OTT streams and for this we needed a solid Time Series Database. Initially, we were using Elasticsearch but once we needed to scale up, we consistently faced latency issues. So we needed a Time Series database that could handle the load of billions of rows every day. We decided to give TimescaleDB a try and there also we faced multiple issues regarding latency. Then we discovered QuestDB and it was a game changer for us. After initial analysis, we found that QuestDB is more performant than Timescale and Elasticsearch, so we decided to give it a chance. Our use case was to ingest 3 million rows per second and QuestDB was able to handle this load easily. We have been using QuestDB since 2022 now and we never looked back for another database. Review collected by and hosted on G2.com.

What do you dislike about QuestDB?

We have been using QuestDB for the last two years and haven't found any issues so far. Review collected by and hosted on G2.com.

What problems is QuestDB solving and how is that benefiting you?

We are an OTT company, so we need to collect CDN logs and analyze them to find the most streamed contents. These logs come according to timestamp, so we needed a time series database. Initially, we were ingesting 5k rows per second and Elasticsearch was sufficient for this use case, but as scale grew, we needed a more performant database. For this, we conducted analysis on Timescale and QuestDB. With QuestDB, we were able to ingest 3 million rows per second with minimal delay. With Timescale, while we were facing latency on simple group by queries (up to 30 seconds), QuestDB was able to perform the same queries under 500 milliseconds. So to summarize, we needed both a read and write performant DB, and QuestDB was able to achieve both. Review collected by and hosted on G2.com.