Riko

Languages and libraries

stream processing library

SHOW HN2016

Legend

Riko

A Python stream processing engine modeled after Yahoo! Pipes

github.com

#stream processing#python#yahoo pipes#etl#rss

283points
67comments
#74of 2,264 in 2016
Top 4%of 2016 by points

How HN took it

LovedMost comments that take a side are positive

5 positive, 11 neutral or asking, 0 mixed, 0 critical, out of 16 comments about the project. Thread score +0.27.

Idea: 2 for, 0 againstDesign: 1 for, 0 againstDocs: 1 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Readme is well done and could guide other projects

    From 1 comment
  • Brings back Yahoo Pipes in a Python library

    From 2 comments
    • I was a heavy user of pipes and I'm now a heavy user of python. I have built my own dodgy simple replacement for some of the things I used to rely on pipes for. I'm very eager to…
      Fuzzwah on HN
    • While I didn't use yahoo pipes too often, I loved it. Having this as a python library (I'm trying to get deeper into python), is great! Kudos and good luck!
      mxuribe on HN
  • Functional API is succinct compared to class-based alternatives

    From 1 comment
    • Interesting project. I hadn't come across this one yet. One difference that riko has is it's based around functions whereas this library (and practically every stream processing…
      reubano on HN

Objections

  • Pull-based generator design can't fan out without loading data into memory

    From 1 comment
    • Cool! I actually starred your project last year. Never really got around to looking under the hood though. How do you handle the "multiple destinations" part? In python you can…
      reubano on HN
  • Push model is easier and enables back pressure

    From 2 comments
    • Python 3.5 introduced the async/await syntax, I don't do C# but at a glance it's the same. I've been working on a similar project and I've also found the push model easier.
      greenshackle on HN
    • Another benefit of the push model is that back pressure becomes much easier to implement.
      infinite8s on HN

Requests

  • Add a GUI

    From 2 comments
    • if 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…
      tudorw on HN
    • 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]…
      reubano on HN
  • Dask integration for distributed processing

    From 1 comment
    • Can 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.…
      tanlermin on HN
  • Twitter support

    From 1 comment
    • Looks nice. Are there any plans for twitter support?
      satai on HN

Questions

  • What kinds of applications people use it for

    From 1 comment
    • Looks interesting. What kind of applications do people use this for?
      et2o on HN
  • Whether it will integrate with Apache Beam

    From 1 comment
    • This is really interesting. Have you looked at Apache Beam? What I think is interesting about Beam -in this specific context- is that it has a standalone runner (java), that…
      ecesena on HN

Alternatives named

  • Yahoo Pipes

    From 1 comment
    • Nice project. I wrote something similar in C# long time ago [1]. Mostly to monitor job feeds and craigslist [2] :-) It supports RSS and Atom, async, various filters,…
      olviko on HN
  • Motorway

    From 1 comment
    • If you're looking for a stream processing engine more close to Storm, etc. but also simple, check out Motorway: https://github.com/plecto/motorway :-)
      oellegaard on HN
  • Node-RED

    From 1 comment
  • Apache NiFi

    From 1 comment
    • Apache Nifi looks promising. https://nifi.apache.org
      qw on HN
  • Apache Beam

    From 1 comment
    • This is really interesting. Have you looked at Apache Beam? What I think is interesting about Beam -in this specific context- is that it has a standalone runner (java), that…
      ecesena on HN
  • Plagger

    From 1 comment
    • I am still a user of Plagger [1], but development halted quite some time ago. Maybe this could be a good replacement. [1] https://github.com/miyagawa/plagger
      raimue on HN
  • Apache Camel

    From 1 comment
    • Also in this space (and worth looking at for inspiration, especially for other potential sources and sinks of data) - Apache Camel [1]. [1]: http://camel.apache.org/
      svieira on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/12136011)