I had not heard of QuestDB. We are considering moving our InfluxDB databases to PostgreSQL with Timescale. Is QuestDB something we should consider before making the switch? Perhaps more importantly, is it stable?
Hi! The performance gap between questDB on both ingestion and queries versus timescale or influx is very significant (orders of magnitude faster). questDB is being used in production for critical use cases at large companies and is definitively stable. Watch out for our new release next week
I guess I was more interested in finding out whether questDB is mature for production use.
The product is impressive, but it looks like the documentation has some way to go. This is often indicative of the maturity of the product itself.
I was very interested in the Postgres wire protocol and its usage.
This part does not seem to be very mature.
Examples:
* The documentation doesn't mention a word of the default username/password on port 8812. I had to find this on a mailing list somewhere after 10 minutes of googling. Has this been hardcoded into the code?
* If you were to connect a typical Postgres tool this port, you'd be able to do selects but not even see the tables. If using psql and doing \d I get:
Ingestion rate is pretty good in Influx and we are happy with that for now. If QuestDB is better I definitely won't complain. The issues with Influx is data integrity and also the difficulty in manipulating time series data if that becomes an issue (e.g turning all "0" string values into a 0i). How does QuestDB fare in this regard?
We take data integrity very seriously. This is one of the reasons QuestDB actually exists. We haven't had reports of data corruption or loss yet. We can commit durably if needed too.
To manipulate data we support "add" and "delete" column on the fly. We can also add column replace and type change if needed. This is pretty easy to do.
PostgreSQL wire is in beta. It works with JDBC driver and we will add metadata support quite soon.
Site owner here. There have been a couple of reports of being re-directed to ... call we say inappropriate material. So far I cannot reproduce this, and can see no reason why it might be happening. IF this happens to you, please feel free to reach out to me directly davidgs[at]davidgs[dot]com and I will work with you to get to the bottom of it.
Very interesting, but can anyone explain the underlying technology?
There are no free lunches.
Here we have sql join on time series data. Very cool, but is it really sustainable?
Under the hood is a stack written from scratch without any dependencies - all libraries have been rewritten. It's in boring Java (zero-GC) and C++ for high performance components such as SIMD instructions. The idea being to provide massive performance and accessibility through SQL. IoT/monitoring being one of the use cases that work particularly well for questdb
Site-owner here. Went and checked everything. Can't find anything that would cause this, so please a) accept my apologies and b) give it one more shot. OR try dev.to/davidgs where it is reposted.
“QuestDB is an open source database which makes time-series fast and easy.”