4 ms·
> Effortlessly handling hundreds of terabytes of data on a single machine Single machine, because it can't handle parallel queries, at all, and there are no op
by spopejoy 7y ago
> Effortlessly handling hundreds of terabytes of data on a single machine
Single machine, because it can't handle parallel queries, at all, and there are no options to scale it.
Every financial institution I've worked at is busily unwinding their investment in q/kdb. It's legacy tech.
- Volt 7y agoWhat are they moving to?
- spopejoy 7y agoOther TS products like OneTick, RDBMSs for TAQ (esp. if you need non-TS indexes), streambase for UI backends I even met a programmer who hacked something together in Java using the same columnar kdb layout but, you know, multithreaded, so different basket optimization jobs could run simultaneously on the same store.