go-waitgroup alternatives and similar packages
Based on the "Goroutines" category.
Alternatively, view go-waitgroup 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. -
-
concurrency-limiter
Concurrency limiter with support for timeouts , dynamic priority and context cancellation of goroutines. -
conexec
A concurrent toolkit to help execute funcs concurrently in an efficient and safe way. It supports specifying the overall timeout to avoid blocking. -
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 go-waitgroup or a related project?
README
go-waitgroup
How to use
An package that allows you to use the constructs of a sync.WaitGroup to
create a pool of goroutines and control the concurrency.
Using it is just like a normal sync.WaitGroup. The only difference is the initialisation. When you use waitgroup.NewWaitGroup, you have the option to specify it's size.
Any int which is bigger than 0 will limit the number of concurrent goroutines. If you specify -1 or 0, all goroutines will run at once (just like a plain sync.WaitGroup).
package main
import (
"fmt"
"net/http"
"github.com/pieterclaerhout/go-waitgroup"
)
func main() {
urls := []string{
"https://www.easyjet.com/",
"https://www.skyscanner.de/",
"https://www.ryanair.com",
"https://wizzair.com/",
"https://www.swiss.com/",
}
wg := waitgroup.NewWaitGroup(3)
for _, url := range urls {
wg.BlockAdd()
go func(url string) {
defer wg.Done()
fmt.Printf("%s: checking\n", url)
res, err := http.Get(url)
if err != nil {
fmt.Println("Error: %v")
} else {
defer res.Body.Close()
fmt.Printf("%s: result: %v\n", url, err)
}
}(url)
}
wg.Wait()
fmt.Println("Finished")
}
Using closures
There is also a way to use function closures to make it even more readable:
package main
import (
"fmt"
"net/http"
"github.com/pieterclaerhout/go-waitgroup"
)
func main() {
urls := []string{
"https://www.easyjet.com/",
"https://www.skyscanner.de/",
"https://www.ryanair.com",
"https://wizzair.com/",
"https://www.swiss.com/",
}
wg := waitgroup.NewWaitGroup(3)
for _, url := range urls {
urlToCheck := url
wg.Add(func() {
fmt.Printf("%s: checking\n", urlToCheck)
res, err := http.Get(urlToCheck)
if err != nil {
fmt.Println("Error: %v")
} else {
defer res.Body.Close()
fmt.Printf("%s: result: %v\n", urlToCheck, err)
}
})
}
wg.Wait()
fmt.Println("Finished")
}
Handling errors
If you want to handle errors, there is also an ErrorGroup. This uses the same principles as a normal WaitGroup with a small twist.
First of all, you can only add functions which returns just an error.
Second, as soon as one of the queued items fail, the rest will be cancelled:
package main
import (
"context"
"fmt"
"os"
"github.com/pieterclaerhout/go-waitgroup"
)
func main() {
ctx := context.Background()
wg, ctx := waitgroup.NewErrorGroup(ctx, tc.size)
if err != nil {
fmt.Println("Error: %v")
os.Exit(1)
}
wg.Add(func() error {
return nil
})
wg.Add(func() error {
return errors.New("An error occurred")
})
if err := wg.Wait(); err != nil {
fmt.Println("Error: %v")
os.Exit(1)
}
}
You can also add multiple functions in one step:
package main
import (
"context"
"errors"
"fmt"
"os"
"github.com/pieterclaerhout/go-waitgroup"
)
func main() {
ctx := context.Background()
wg, ctx := waitgroup.NewErrorGroup(ctx, tc.size)
if err != nil {
fmt.Println("Error: %v")
os.Exit(1)
}
wg.Add(
func() error {
return nil
},
func() error {
return errors.New("An error occurred")
},
)
if err := wg.Wait(); err != nil {
fmt.Println("Error: %v")
os.Exit(1)
}
}
*Note that all licence references and agreements mentioned in the go-waitgroup README section above
are relevant to that project's source code only.