3 ms·
> It's not expensive when dimensions are just columns in the custom table schema, like for example in TimescaleDB or kdb+/q. kdb+/q (not exactly sure) is the o
by hardwaresofton 5y ago
> It's not expensive when dimensions are just columns in the custom table schema, like for example in TimescaleDB or kdb+/q.
kdb+/q (not exactly sure) is the one that is used heavily in finance, correct?
[EDIT] - Yup[0][1]. I'm not sure how many competitors there are but last time I heard about kdb it seemed like they were pretty much the go-to choice outside comp sci land (which is normally preoccupied with influx, prometheus, timescale, etc).
There's probably a reason it's trusted by those other fields.
[0]: https://kx.com/ https://kx.com/
[1]: https://code.kx.com/home/ https://code.kx.com/home/
- liveoneggs 5y agokdb is crazy expensive which is why storing your 5-min load average inside of it doesn't make much sense
- nivertech 5y agokdb+/q was originally heavily used in finance/trading, but nowadays also in IoT/IIoT. The q language itself is pretty-much general purpose PL, but of course it shines for timeseries processing workloads.