heka
DEPRECATED: Data collection and processing made easy. (by mozilla-services)
go-parallel
parallelism in Go using generics (by gregwebs)
| heka | go-parallel | |
|---|---|---|
| 1 | 1 | |
| 3,399 | 2 | |
| - | - | |
| 0.0 | 4.1 | |
| over 1 year ago | 2 months ago | |
| Go | Go | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
heka
Posts with mentions or reviews of heka.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-11-25.
-
Show HN: Rill – Composable concurrency toolkit for Go
The channel-focused approach to stream processing reminds me of Heka [0]. It was a contemporary of Samza and Heron, and it was fairly prominent in the early Go ecosystem (maybe 10 years ago). As I recall it, quite foggily and quite a long while later, one of the final nails in Heka's coffin was that channel throughput didn't scale well. Do you have benchmarks for Rill, or is it not intended for high-throughput use cases?
[0]: https://github.com/mozilla-services/heka
go-parallel
Posts with mentions or reviews of go-parallel.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-11-25.
-
Show HN: Rill – Composable concurrency toolkit for Go
I don't like how errors are retrieved rather than assigned because assignment gets verified by tools. In my library I used a channel for errors- that gives ultimate flexiblitiy- it can be converted to wait and collect them to a slice or to perform a cancellation on first error.
[1] https://github.com/gregwebs/go-parallel
What are some alternatives?
When comparing heka and go-parallel you can also consider the following projects:
toxiproxy - :alarm_clock: :fire: A TCP proxy to simulate network and system conditions for chaos and resiliency testing
rill - Go toolkit for clean, composable, channel-based concurrency
Gor - GoReplay is an open-source tool for capturing and replaying live HTTP traffic into a test environment in order to continuously test your system with real data. It can be used to increase confidence in code deployments, configuration changes and infrastructure changes.
semgroup - Like errgroup/waitgroup, but only runs a maximum of tasks at any time.
Fluentd - Fluentd: Unified Logging Layer (project under CNCF)
cff - Concurrency toolkit for Go