Open justcodebase opened 6 months ago
We do not have enough incentive so far to keep julia client moving. But am very curious to know the usecase for sending data from julia to QuestDB?
I'm very sorry for the delay in my reply, it was unintentional. Regarding the use case, my setup consists of BeeGFS, Redpanda, MigratoryData Kafka Edition, Arroyo, a bit of Rust, Julia, MindsDB and indeed QuestDB. I came across your repository and based on my preliminary tests, I concluded that it seems to be a super-fast Julia QuestDB Client. Thus, I would like to sustain my interest. My major use case is a hobby project about algorithmic trading. In particular, as of now, I am interested in Extended Kalman Filter, Vine Copula, and Merger Arbitrage Mispricing Strategies. I'm new to those topics.
@Ochibobo, @quinnj, @rbeeli
Guys, I am wondering what you think about this package (if I may ask such a question). I took a preliminary look, and in my opinion, it seems to be very performant. Would you please consider helping me maintain it? I am asking because it is way too advanced compared to my coding skills, but I am willing to learn and help as much as possible.
Hi @justcodebase Unfortunately, I don't have the time to contribute here, I'm also not a user of QuestDB. If you are looking for a high-performance time series DB, I can recommend ClickHouse, it also has a Julia client.
Hi @rbeeli, Thank you very much for the reply. I really appreciate it. Initially, I looked at ClickHouse and Timeplus Proton, but I decided to try QuestDB and Arroyo. I will take your advice seriously and take another look at ClickHouse. Nevertheless, I think there is a lot to like about QuestDB, especially its native support for the financial sector, as well as its GUI and charting abilities. I also had some hopes regarding the fact that it leverages HTTP instead of TCP.
Hello @justcodebase,
Sorry for the late response. I had worked on another client a while back QuestDBClient.jl in pure Julia but after a while, the QuestDB team seemed to focus on the Rust client. This means to make the most out of things, I would have had to write a wrapper around the Rust client. I'm not sure if thing are the same now as they were then.
Have you tried reaching out to the team via Slack (I'm assuming the channel is still operational).
Having said that, it's been long since I last played with QuestDB, though I really appreciate the simplicity and novelty of their approach. I might not be of much help now.
All the best.
Hello @Ochibobo,
Thank you very much for your kind reply. Yes, I am aware that you are the author of QuestDBClient.jl
. Actually, I discovered this database initially through the blogs of @dm13450 (one of the two prominent Julia whales I am aware of), then indeed by using your QuestDBClient.jl
, and finally, I arrived at this page by @BrandonEscamilla and @amunra. I would like to underline that I share your opinion about the simplicity and novelty of QuestDB
.
I believe that official support for a Julia
QuestDB
Client
would be beneficial for both QuestDB
and the Julia
ecosystem at large. I am not a professional coder; nevertheless, I would like to reiterate that I would be happy to assist with any potential development of such a client. However, please kindly be informed that I can't do it on my own as it is slightly beyond my current coding abilities. Since QuestDB
appears to be high-performance, and as I understand it, with the upcoming Julia
support for FPGAs
, I would like to mention @StefanKarpinski. Maybe he knows somebody who might be interested in such a project (I really hope that he does not mind such a ping). Again, I believe that strengthening Julia's
position in sectors involving general-purpose moving particles
and sensor data
(both industrial and educational segments) could be to Julia's
advantage.
In summary, I must admit that I do not fully understand the current situation. It seems to me that there are two Julia
QuestDB
clients under development, one registered and the other not. And there seems to be no official support.
All the best.
I'd like to kindly ask if there is any chance for a RC? I'm also wondering if you are planning to leverage HTTP instead of TCP in the upcoming version?