News for hackers. Stuff that matters.
Re:Why we used Pony to write Wallaroo by jack9 on Thursday October 26, 2017 @03:10PM (#15562037)
How do you ingest data with Wallaroo? I see a mention of "...say TCP" and in the github word count there is mention of a (data)source framed-message-protocol but nothing that describes it in the (https://github.com/WallarooLabs/wallaroo/blob/0.2.0/book/cor...) link.

Dropping Python into the mix for a high throughput processing pipeline seems counterproductive. Why isn't there a tutorial in a more strict language like Go or C++, since someone pursuing this kind of high-throughput framework that can't benefit from wider parallelism, will 100% want that performance guarantee?

Re:Why we used Pony to write Wallaroo by spooneybarger on Thursday October 26, 2017 @04:39PM (#15562803)
Ingestion:

Kafka and framed TCP are the two ingestion sources that Wallaroo currently ships with.

Python:

We added a Python API because there was a lot of interest in it. There's more to Wallaroo than just performance and folks were interested in having it available via Python. See https://vimeo.com/234753585 for some more information on the "scale independent" nature of the Wallaroo APIs.

Go:

We're working on that right now actually. Planning to release later this year.

C++:

We had a C++ API (still do), we aren't currently supporting it. There was limited interest at the time. If folks show interest we would start supporting it again.