channelify alternatives and similar packages
Based on the "Goroutines" category.
Alternatively, view channelify alternatives based on common mentions on social networks and blogs.
-
-
goworker
goworker is a Go-based background worker that runs 10 to 100,000* times faster than Ruby-based workers. -
pool
:speedboat: a limited consumer goroutine or unlimited goroutine pool for easier goroutine handling and cancellation -
go-workers
DISCONTINUED. ๐ท Library for safely running groups of workers concurrently or consecutively that require input and output through channels -
async
A safe way to execute functions asynchronously, recovering them in case of panic. It also provides an error stack aiming to facilitate fail causes discovery. -
-
gollback
Go asynchronous simple function utilities, for managing execution of closures and callbacks -
Hunch
Hunch provides functions like: All, First, Retry, Waterfall etc., that makes asynchronous flow control more intuitive. -
gpool
gpool - a generic context-aware resizable goroutines pool to bound concurrency based on semaphore. -
gowl
Gowl is a process management and process monitoring tool at once. An infinite worker pool gives you the ability to control the pool and processes and monitor their status. -
routine
go routine control, abstraction of the Main and some useful Executors.ๅฆๆไฝ ไธไผ็ฎก็Goroutine็่ฏ๏ผ็จๅฎ -
kyoo
Unlimited job queue for go, using a pool of concurrent workers processing the job queue entries -
execpool
A pool that spins up a given number of processes in advance and attaches stdin and stdout when needed. Very similar to FastCGI but works for any command. -
-
conexec
A concurrent toolkit to help execute funcs concurrently in an efficient and safe way. It supports specifying the overall timeout to avoid blocking. -
concurrency-limiter
Concurrency limiter with support for timeouts , dynamic priority and context cancellation of goroutines. -
queue
package queue gives you a queue group accessibility. Helps you to limit goroutines, wait for the end of the all goroutines and much more. -
hands
Hands is a process controller used to control the execution and return strategies of multiple goroutines. -
async-job
AsyncJob is an asynchronous queue job manager with light code, clear and speed. I hope so ! ๐ฌ
InfluxDB - Purpose built for real-time analytics at any scale.
Do you think we are missing an alternative of channelify or a related project?
README
channelify
This library helps you to transform any function into a function that returns a any type to a function that return such types within a channel. This is useful to run in parallel multiple functions and have control on the returned values.
Channelify uses go routines to parallelize the execution of the functions.
The idea comes from Javascript Promisify utility that transforms a callback into a promise.
Installation
go get github.com/ddelizia/channelify
Usage example
Here an example of transforming a simple function in channel so you can execute multiple functions in parallel:
fn := func () string {
time.Sleep(time.Second * 3)
return "hello"
}
ch1 := Channelify(fn)
ch2 := Channelify(fn)
chV1 := ch1.(func () chan string)()
chV2 := ch2.(func () chan string)()
v1, v2 := <- chV1, <- chV2
If your functions returns multiple values you can use as follow:
fn1 := func (hello string) (string, error) {
time.Sleep(time.Second * 2)
fmt.Println(hello)
return hello, nil
}
fn2 := func (hello string) (string, error) {
time.Sleep(time.Second * 3)
fmt.Println(hello)
return hello, nil
}
ch1 := Channelify(fn1)
ch2 := Channelify(fn2)
chV1, chE1 := ch1.(func (string) (chan string, chan error))("hello1")
chV2, chE2 := ch2.(func (string) (chan string, chan error))("hello2")
v1, e1, v2, e2 := <- chV1, <- chE1, <- chV2, <- chE2
fmt.Print(v1, e1, v2, e2)
Contributing
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request
*Note that all licence references and agreements mentioned in the channelify README section above
are relevant to that project's source code only.