Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
11–20 of 69 posts
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#12Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#13if someone can spin up a usable gui, charge enough to make a living without compromising on performance, promise some longevity and a way to export of my stuff I would probably pay for that, I loved pipes, the GUI was a big deal for me.
[1] https://azkaban.github.io/ [2] https://developers.google.com/blockly/ [3] http://nodered.org/
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#14This is absolutely beautiful. Love the fact that it's using RSS for this.
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#15If you're looking for a stream processing engine more close to Storm, etc. but also simple, check out Motorway: https://github.com/plecto/motorway :-)
I personally prefer the functional approach much better. And if you compare the word count examples on the respective readmes [1, 2], you will see riko is much more succinct. But I suppose the verbosity of the other libraries come with benefits like scaling across a cluster of servers.
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#16if someone can spin up a usable gui, charge enough to make a living without compromising on performance, promise some longevity and a way to export of my stuff I would probably pay for that, I loved pipes, the GUI was a big deal for me.
Have you investigated any of the existing GUIs? [1-3] I'd love to hear your thoughts on their pros/cons. I do plan to integrate a nice GUI framework if I can find one. [1] https://azkaban.github.io/ [2] https://developers.google.com/blockly/ [3] http://nodered.org/
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#17Earlier quoted context omitted.
Have you investigated any of the existing GUIs? [1-3] I'd love to hear your thoughts on their pros/cons. I do plan to integrate a nice GUI framework if I can find one. [1] https://azkaban.github.io/ [2] https://developers.google.com/blockly/ [3] http://nodered.org/
Node-RED is pretty great. I think a wiring interface is a better choice than a block-level thing like blockly.
Which interface do you think is more newbie friendly? My gut says blocks (maybe something a bit more simple/refined than blocky) are easier to grok, while wires allow for designing more complex workflows.
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#18It can handle parallel and distributed parts for you.
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#19Can you consider Dask integration? http://distributed.readthedocs.io/en/latest/queues.html https://github.com/dask/dask It can handle parallel and distributed parts for you. https://github.com/dask/dask
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#20`riko` is pure python stream processing library for analyzing and processing streams of structured data. It's modeled after Yahoo! Pipes [1] and was originally a fork of pipe2py [2]. It has both synchronous and asynchronous (via twisted) APIs, and supports parallel execution (via multiprocessing). Out of the box, `riko` can read csv/xml/json/html files; create text and data based flows via modular pipes; parse and ex…
Yahoo Pipes was a nice project, but as its popularity grew, it started getting blocked more and more. It was also hard to build and maintain pipelines with more than a few steps.
[1] https://github.com/olviko/RssPercolator
[2] https://github.com/olviko/RssPercolator/blob/master/RssPerco...