EIeikenberry·Sep 19, 2016
I've been keeping an eye on this one for the next time I needed a system of this sort. Looks promising...
https://github.com/chrislusf/glow
In Scalable Stream Processing: A Survey of Storm, Samza, Spark and Flinkchrislusf
glow
Go2016–2016
chrislusf / glow
glow
Glow is an easy-to-use distributed computation system written in Go, similar to Hadoop Map Reduce, Spark, Flink, Storm, etc. I am also working on another similar pure Go system, https://github.com/chrislusf/gleam , which is more flexible and more performant.
2Distinct people
2Mentions
0Explicit recommenders
3.2KGitHub stars
What to know before exploring
What it is
Glow is an easy-to-use distributed computation system written in Go, similar to Hadoop Map Reduce, Spark, Flink, Storm, etc. I am also working on another similar pure Go system, https://github.com/chrislusf/gleam , which is more flexible and more performant.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month2 dated mentions
Observed mentions: 2016-01-02 15:02:18 UTC to 2016-09-19 01:02:51 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 2016 | 2016-01-01 00:00:00 UTC | 2016-02-01 00:00:00 UTC | 1 | 0 | 1 |
| Feb 2016 | 2016-02-01 00:00:00 UTC | 2016-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2016 | 2016-03-01 00:00:00 UTC | 2016-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2016 | 2016-04-01 00:00:00 UTC | 2016-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2016 | 2016-05-01 00:00:00 UTC | 2016-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2016 | 2016-06-01 00:00:00 UTC | 2016-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2016 | 2016-07-01 00:00:00 UTC | 2016-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2016 | 2016-08-01 00:00:00 UTC | 2016-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2016 | 2016-09-01 00:00:00 UTC | 2016-10-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesGlow: Map Reduce for Golang
I enjoyed reading this post. What especially surprised me is, how easy it is to get going with Glow.
One caveat with the standalone example though is: You need to install Glow first (even though this is a one-liner and appears later in the tutorial)
You addressed the static nature of Glow data flows but also mentioned, that it is possible to do fix-point iteration (by the example of a linear regression). I would love to see an example for such a data flow. I've looked up the examples on [1] and [2] but didn't see one.
As I get it, it is also possible to branch a data flow depending on the result of a condition (if-then-else). Is there an example for this?
Wouldn't it be possible to do even general recursion with this programming model? (I can't come up with a reason why not if the aforementioned things work.)
I
Read the rest
t is possible to use distributed file systems (like HDFS) as well as distributed databases (like MongoDB) as data sources and intermediate data, as I get it, is sent via channels between processes. If such a channel breaks (e.g., because of a network partition) is there a some kind of failover (rescheduling, making sure a recovering process doesn't break the data flow, ...)? Any plans incorporating Hystrix?
This is great stuff. I'm looking forward to read more about Glow.
[1] https://github.com/chrislusf/glow
[2] https://github.com/postfix/glow_examples