Jonny Press
KX recently announced the public preview of KDB-X, the next generation of their kdb+ platform. You can find the details here, but in short: it looks and feels a lot like kdb+ for now, but the roadmap is exciting.
The big change is that KDB-X is free for commercial use, which opens up a lot of new possibilities for teams and businesses of all sizes. From a feature point-of-view what caught our attention is Parquet integration, AI libs, and modules. The public preview was recently extended to include module support- it’s been an ask for many years, it’s great to see it finally here.
As fans of open-source, we are working with KX to seed the environment with a set reusable, well-documented, tested libraries that we think will be useful to anyone working in the space. We will do this development in public, on Github. Some prioritisation guidance from the wider community would be much appreciated.
We’ve started putting together some options, most of which we have a start point for in the TorQ codebase- click the link below for the start point.
| Module | Category | Start Point | Description | Priority | Status |
|---|
The “Priority” status in the table above stems from the order that we think we would need them if we were composing a kdb+ system from scratch. But we don’t want to just build what we think is useful. We’d rather hear what you need. If you’re planning to try out KDB-X, or are already using it, we’d really appreciate your feedback on which modules would make the biggest difference to your team.
Let us know what would help you most. Whether that’s improving common workflows, replacing scripts you’ve built repeatedly, or ideas we haven’t thought of yet. You can do that by contributing on the discussion forum in Github. The discussion forum contains more detail on each of the modules, and you can review the progress that we have made so far. Contributions could be feedback, suggestions, or upvotes etc. We’ll use upvotes to help us prioritise. We would love code reviews and contributions too!
Share this: