<SeanTAllen>
our python API has been getting far more interest than the Go one so we decided not to update the Go API for now.
<SeanTAllen>
have you been using the Go API with Wallaroo?
<tumasgiu>
that's what I guessed
<tumasgiu>
yes i have been using the go api
<SeanTAllen>
we've never heard from anyone in the open source community who was. it can be hard to make decisions in a vacuum.
<SeanTAllen>
what have you been doing with the Go API?
<tumasgiu>
I prototyped a few pipelines for parsing logs, I'm researching possible solutions for the underlying infrastructure of a security focused platform we are developping
<SeanTAllen>
what possible solutions have you been looking at?
<tumasgiu>
The classics at first, kafka, ELK and the likes, but they are very heavy
<tumasgiu>
and your apporach makes it easy to scale different aspects of the plaform indenpendently
<SeanTAllen>
that's good to hear. so, everything is still there in the 0.5.4. we aren't planning on updating it in the near future, but if we see people starting to use the Go API, we'd definitely look at updating it to the new API.
<SeanTAllen>
being noisy and letting us know what you are doing and what you are using and what you need can definitely get results.
<SeanTAllen>
when did you first start playing around with Wallaroo?
<SeanTAllen>
what made you pick up the Go API instead of the Python one?
<tumasgiu>
ok, thanks very much for the info
<tumasgiu>
I started playing 2 weeks ago
<tumasgiu>
and i used the go api because it's my goto language at the moment
<tumasgiu>
and i dont' know python
<tumasgiu>
i have people in my team "speaking" python though
<tumasgiu>
so we could switch to the python api now to be on safe side
<SeanTAllen>
Well, the python API has the same approach as the Go one, so its really a matter of language.
<SeanTAllen>
for your log parsing, do you have any idea what the workload would look like in terms of messages you are processing a second and how long it takes to process one?
<tumasgiu>
No precise idea yet, but It looks like it's gonna be in the 1TB/day ballpark
<SeanTAllen>
That's a terrabyte of logs?
<tumasgiu>
on my proto i can process about 3 to 4k messages /sec
<tumasgiu>
yes
<SeanTAllen>
does 3 to 4k a second feel like something that would get the job done?
<tumasgiu>
it seems, that is with just a node running on my dev machine, i haven't run more advanced experiments for now
<SeanTAllen>
well, if you run into issues, we are around and we'd love to get your feedback as you move forward. feedback from users helps us a great deal in setting direction etc.
<SeanTAllen>
im heading up developer relations work these days, so if you need anything, feel free to email me sean@wallaroolabs.com.
<tumasgiu>
alright good to know, i definitively will keep in touch and give you feedback