QuestDB Cloud

What do you like best about the product?

QuestDB fits our needs. We handle and analyze large datasets of cell growth data with measurements over time, often as CSV files. This time-series-based database fits our use case very well. By importing it into an SQL database, developers can quickly implement a convenient and known way to get statistics from selections made in the front end.
We look forward to integrating streaming data from measurements into the database at a later point, but we are not there yet. We know that it is possible in this setup.

Also, the Slack channel is friendly, and the direct contact with developers is excellent.

What do you dislike about the product?

I have nothing big to complain about, but if I have to complain about something, there was one non-backwards-compatible upgrade. It was fixed on our side but unexpected from the usually very stable product development.

What problems is the product solving and how is that benefiting you?

As our data is a time series, it fits our needs like a hand in a glove. Also, the automatic CSV import made our development time significantly shorter, saving the company a lot of money.

What do you like best about the product?

Our project have been using Solr as a statistics data storage for years. It was not a right decision because Solr is not good solution for realtime data processing. The best approach in our case is a time series database. Using such DB in embedded mode was another important requirement. There are a lot of competitors in this market, but QuestDB was the only one who offers embedded mode. So we gave a chance to QuestDB and never regreted.
It`s great to see the rapid evolution of QuestDB. The developers team constantly introduces new features, improvements and bug fixes.
Also want to note an excellent support. The ability to ask a question directly to developers and get answer in Slack channel is a really cool.

What do you dislike about the product?

Actually the embedded mode chapter looks to be the smallest part of documentation. It would be nice to add some best practice advices and code examples.

What problems is the product solving and how is that benefiting you?

The biggest problem to solve was real time processing and storing statistical data our application collect from various sources. These data should be used for building reports and charts.
QuestDB perfectly fits our needs.

What do you like best about the product?

Byond QuestDB being *incredibly fast*, it's also a joy to use. And more importantly, it's not a pain to use. Other DBs require more ongoing maintenance, troubleshooting, etc. QuestDB truly is a "set it & forget it", trustworthy DB that shines in production workloads.

The inbuilt SQL extensions and curated dialect make writing QuestDB SQL fast, fun, and powerful. The inbult REST support, in addition to the InfluxDB Line Protocol & PG Wire connection methods allow the user to select the best tool for the job.

Being open source, the deployment flexibility is fantastic. The QuestDB team regularly meets with us to ensure we're satisfied, and they regularly ship impactful features.

QuestDB is my definitive go-to for all timeseries needs!

What do you dislike about the product?

The QuestDB web console UI is helpful for adhoc exploration, but does not currently have a means of organizing / saving queries, so it gets messy fast. Additionally, some BI solutions (like PowerBI) or downstream applications can't connect to QuestDB's flavor of PG Wire, so we've had to go through the REST API in these cases. Fortunately, the QuestDB team is on it and anticipates delivering a fix to that soon.

What problems is the product solving and how is that benefiting you?

We've tried Timescale, which simply takes just too much maintenance & configuration to optimize performance and stay agile. QuestDB requires almost no ongoing configuration because it ships incredibly fast by default. QuestDB eliminates the friction in storing & querying timeseries data.

What do you like best about the product?

I had invested a lot of time prototyping a project with another time-series database and was finding a lot of pain points. I decided to give QuestDB a go, and the transition process was really easy and most of the issues I had with the other DB simply went away. Additionally, I gained valuable time when my application starts and has to read current state from the DB... QuestDB delivered my data in half the time the other DB did. I also like the SQL syntax - it's just one less new thing I need to pick up when starting with QuestDB. The free/open source version is great for my purposes.

What do you dislike about the product?

Documentation is pretty good, but I would like to see some more around best practices, particularly with how to design a schema that is optimal for my needs.

What problems is the product solving and how is that benefiting you?

I need to keep track of the current state of about one million data points that change over time. QuestDB had made this simple to do.

What do you like best about the product?

+ Very fast
+ Extremly feature rich
+ Nice time Zone Handling integrated
+ Very fast en knowledgable support
+ Easy to setup

What do you dislike about the product?

- Limited regions in their cloud offering

What problems is the product solving and how is that benefiting you?

We were strugling to find a database which allows us to handle time series from different time zones. We really love the fact that you can align all the data to a specific time zone at query time. This saved us hours of coding.