5 ms·
To the QuestDB founders - thanks for the blog post & benchmarks! I had a question about this part: > We found out that this model does not fit all data acquis
by shay_ker 5y ago
To the QuestDB founders - thanks for the blog post & benchmarks!
I had a question about this part:
> We found out that this model does not fit all data acquisition use cases, such as out-of-order data
I know the whole blog post is about how you're now able to handle out-of-order data, but I'm curious - what use cases is QuestDB best for? Can you provide some concrete examples of where customers have ordered data and need QuestDB?
- the_arun 5y agoBy reading their home page, I thought QuestDB could be very useful for audit logs in an application where we need a picture of journey line for every entity we care.
- nhourcard 5y agoIndeed! One can think of time series data as consecutive events happening such as logs, where the series is going to give the historical evolution over time.
- dikei 5y agoIt's in their tag line > QuestDB is the fastest open source time series database Time series data is any type of data that always has a timestamp attached to it, such as logging, metrics, telemetry, etc.
- ludston 5y agoYou get similar functionality to QuestDB if you take a traditional database, make all of your tables clustered by datetime fields. The advantage advertised by QuestDB is that it is optimized specifically for this common use-case. The disadvantage of this being that it only allows clustered indexes for timestamp columns.
- dikei 5y agoI agree, you can use traditional RDBMS like Postgresql or MySQL for almost every use cases. It's just that purpose-built DBs like QuestDB can be multi-magnitude faster if your problem fit their niche.
- nhourcard 5y agoThanks for the kind words! QuestDB co-founder here - one example in fintech where you are polling multiple end points simultaneously for market data acquisition. You can think of multiple financial exchanges sending the data, but the latency varies for each venue. This is a great article written by one of our contributors about ingesting data from multiple crypto exchanges at the same time [1]. Many firms in financial services and fintech use QuestDB [2] Another would be a manufacturing firm with thousands of sensors sending data to the database continuously, latency and delivery mechanism mean that timestamps often arrive out of order. There is a case study we did with CNC machines manufacturer DATRON [3]. Tracking moving vehicles (say cars, ships, drones, planes) on a map where the two primary axis are time and space - if you want to see the position of those vehicles in the past, you want to have the timestamps ordered. Finally you can think of typical devops/monitoring/alerting use cases. Verizon uses QuestDB to monitor metrics for autoscaling decision to their Vespa engine that provides search, recommendation, and personalization to their users [4]. Here you want the series to be ordered by time. [1] https://levelup.gitconnected.com/tracking-multiple-cryptocurrency-exchanges-using-a-timeseries-database-6b13cc7e8490 https://levelup.gitconnected.com/tracking-multiple-cryptocur... [2] https://www.tradersinsight.news/ibkr-quant-news/optimizing-time-series-databases-for-machine-learning/ https://www.tradersinsight.news/ibkr-quant-news/optimizing-t... [3] https://questdb.io/case-study/datron/ https://questdb.io/case-study/datron/ [4] https://questdb.io/customers https://questdb.io/customers