Earlier quoted context omitted.
This is an implementation of "Flow Based Programming", right? Its a programming paradigm invented before its time IMHO; perfect for a world of streaming data.
> This is an implementation of "Flow Based Programming", right? pretty much.... just without a GUI. My inspiration was method chaining [1] and the first implementation was this [2]. [1] http://martinfowler.com/articles/collection-pipeline/ [2] http://stackoverflow.com/questions/12172934/method-chaining-...
Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
41–50 of 69 posts
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#42Earlier quoted context omitted.
Can’t really remember, sorry, that code was built for processing RSS feeds and data size was never an issue. I will take a look when get some free time… But, I see what you mean. I had to deal with similar issues in commercial projects and the "pull" model (generators in Python ~ "yield return" in C#) almost never a good idea, especially when you have to have concurrent consumers. While callbacks are hard to combine,…
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.
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#43Earlier quoted context omitted.
> This is an implementation of "Flow Based Programming", right? pretty much.... just without a GUI. My inspiration was method chaining [1] and the first implementation was this [2]. [1] http://martinfowler.com/articles/collection-pipeline/ [2] http://stackoverflow.com/questions/12172934/method-chaining-...
I am currently working on an alternative approach which is based on a column-oriented paradigm for in-stream analytics as opposed to flow-orientation. It is an adaptation of DataCommandr ( http://conceptoriented.com ) which is a column-oriented approach to data processing. Unfortunately, StreamCommandr is not yet available but it would be interesting to compare advanatages and drawbacks of these two paradigms.
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#44Earlier quoted context omitted.
This is an implementation of "Flow Based Programming", right? Its a programming paradigm invented before its time IMHO; perfect for a world of streaming data.
> This is an implementation of "Flow Based Programming", right? pretty much.... just without a GUI. My inspiration was method chaining [1] and the first implementation was this [2]. [1] http://martinfowler.com/articles/collection-pipeline/ [2] http://stackoverflow.com/questions/12172934/method-chaining-...
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#45Earlier quoted context omitted.
This is an implementation of "Flow Based Programming", right? Its a programming paradigm invented before its time IMHO; perfect for a world of streaming data.
> This is an implementation of "Flow Based Programming", right? pretty much.... just without a GUI. My inspiration was method chaining [1] and the first implementation was this [2]. [1] http://martinfowler.com/articles/collection-pipeline/ [2] http://stackoverflow.com/questions/12172934/method-chaining-...
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#46Earlier quoted context omitted.
I am currently working on an alternative approach which is based on a column-oriented paradigm for in-stream analytics as opposed to flow-orientation. It is an adaptation of DataCommandr ( http://conceptoriented.com ) which is a column-oriented approach to data processing. Unfortunately, StreamCommandr is not yet available but it would be interesting to compare advanatages and drawbacks of these two paradigms.
I didn't see any code examples so it's a bit difficult to figure out what's going on. Are there any open source column-oriented programming implementations?
StreamCommandr essentially relies on the same principles and changes only external API and some internal processing. The idea is that any data table is like a stream of records so that we add new records and delete outdated records. Simultaniously, we evaluate other columns and tables by performaing potentially complex computations which are difficult to do in a record flow.
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#47if 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.
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#48Also 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/
I don't know if it's bc of the language (java) or something else, but I've never been able to grok apache data projects. I theoretically know what they do, but there's no way I can understand the code, e.g. [1]. [1] http://camel.apache.org/etl-example.html
Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#49Re: Show HN: Riko – A Python stream processing engine modeled after Yahoo! Pipes
#50Is there anything like this available that's based on node.js with a decent GUI?