tunny VS cque

Compare tunny vs cque and see what are their differences.

cque

Go channel que for local workers (by santrancisco)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
tunny cque
2 1
3,770 2
- -
0.0 10.0
about 1 year ago over 5 years ago
Go Go
MIT License MIT License
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.

tunny

Posts with mentions or reviews of tunny. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-24.

cque

Posts with mentions or reviews of cque. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-06-08.
  • Show HN: Tasqueue – A simple, customisable distributed job/worker in Go
    5 projects | news.ycombinator.com | 8 Jun 2022
    Noice! I am keen to give this a go.. the broker code are small and seems easy enough to implement for different backends.

    having a quick glance, it does remind me a lot of que-go (https://github.com/bgentry/que-go) that is inspired by similar project written in ruby which use postgresql lock cleverly to take tasks from queue, work on it and release lock.

    I liked the implementation so much and how easy it was to write worker for it, i ended up modifying it to use go channel (https://github.com/santrancisco/cque) as queue for worker task.. i used it in several personal projects over the years for cli tools that can leverage from having async tasks/jobs handle by workers.

What are some alternatives?

When comparing tunny and cque you can also consider the following projects:

ants - 🐜🐜🐜 ants is a high-performance and low-cost goroutine pool in Go./ ants ζ˜―δΈ€δΈͺι«˜ζ€§θƒ½δΈ”δ½ŽζŸθ€—ηš„ goroutine 池。

Tasqueue - A simple, customisable distributed job/worker in Go

go-do-work - Dynamically resizable pools of goroutines which can queue an infinite number of jobs.

goworker - goworker is a Go-based background worker that runs 10 to 100,000* times faster than Ruby-based workers.

semaphore - 🚦 Semaphore pattern implementation with timeout of lock/unlock operations.

workerpool - Go simple async worker pool

go-floc - Floc: Orchestrate goroutines with ease.

WorkerGo - A worker pool implementation for Go

grpool - Lightweight Goroutine pool

go-waitgroup - A sync.WaitGroup with error handling and concurrency control

pool - :speedboat: a limited consumer goroutine or unlimited goroutine pool for easier goroutine handling and cancellation

Goflow - Simply way to control goroutines execution order based on dependencies