Show HN: Rill – Composable concurrency toolkit for Go

1. conc

   1 27 9,561 5.9 Go

   Better structured concurrency for go

   

   Sourcegraph Conc is broadly similar in providing pool helpers, but doesn't provide the same fine grained batching options: https://github.com/sourcegraph/conc

   Uber CFF does code generation, and has more of a focus on readability and complex dependency chains: https://github.com/uber-go/cff

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. mgmt

   2 43 3,703 9.5 Go

   Next generation distributed, event-driven, parallel config management!

   

   Nice! I do a lot of concurrency work with DAG's in https://github.com/purpleidea/mgmt/ and I would love to swap out some of those concurrency runners with a lib if possible.

   I was wondering if this could be it... Any thoughts in that direction, please let me know!

4. rill

   3 5 1,815 9.9 Go

   Rill is a tool for effortlessly transforming data sets into powerful, opinionated dashboards using SQL. BI-as-code.

   

   This also came to my mind when I heard `rill`, coming from https://www.rilldata.com/ .

5. rill

   4 2 1,492 8.2 Go

   Go toolkit for clean, composable, channel-based concurrency (by destel)

   

6. cff

   5 2 190 6.9 Go

   Concurrency toolkit for Go

   

   Sourcegraph Conc is broadly similar in providing pool helpers, but doesn't provide the same fine grained batching options: https://github.com/sourcegraph/conc

   Uber CFF does code generation, and has more of a focus on readability and complex dependency chains: https://github.com/uber-go/cff

7. tunny

   6 3 3,914 0.0 Go

   A goroutine pool for Go

   There are also libraries like https://github.com/Jeffail/tunny or https://pkg.go.dev/go.uber.org/goleak or https://github.com/fatih/semgroup to help deal with concurrency limits and goroutine lifecycle management.

   As the author of https://github.com/ahmetb/go-linq, it's hard to find adoption for libraries offering "syntactic sugar" in Go, as the language culture discourages those kind of abstractions and keeping the code straightforward.

8. semgroup

   7 2 312 4.1 Go

   Like errgroup/waitgroup, but only runs a maximum of tasks at any time.

   There are also libraries like https://github.com/Jeffail/tunny or https://pkg.go.dev/go.uber.org/goleak or https://github.com/fatih/semgroup to help deal with concurrency limits and goroutine lifecycle management.

   As the author of https://github.com/ahmetb/go-linq, it's hard to find adoption for libraries offering "syntactic sugar" in Go, as the language culture discourages those kind of abstractions and keeping the code straightforward.

9. go-linq

   8 5 3,516 0.0 Go

   .NET LINQ capabilities in Go

   There are also libraries like https://github.com/Jeffail/tunny or https://pkg.go.dev/go.uber.org/goleak or https://github.com/fatih/semgroup to help deal with concurrency limits and goroutine lifecycle management.

   As the author of https://github.com/ahmetb/go-linq, it's hard to find adoption for libraries offering "syntactic sugar" in Go, as the language culture discourages those kind of abstractions and keeping the code straightforward.

10. go-parallel

    9 1 2 3.8 Go

    parallelism in Go using generics

    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

11. heka

    10 1 3,399 0.0 Go

    Discontinued DEPRECATED: Data collection and processing made easy.

    

    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

Suggest a related project