mangos
mangos is a pure Golang implementation of nanomsg's "Scalablilty Protocols" (by nanomsg)
Asynq
Simple, reliable, and efficient distributed task queue in Go (by hibiken)
mangos | Asynq | |
---|---|---|
2 | 32 | |
646 | 8,648 | |
1.1% | - | |
6.2 | 7.0 | |
12 days ago | 3 days ago | |
Go | Go | |
Apache License 2.0 | 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.
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.
mangos
Posts with mentions or reviews of mangos.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-07.
- What would be a good message broker internal to my program?
-
Reconnect to a server
I'm writing a client application that uses https://github.com/nanomsg/mangos to connect to a server using the PUB/SUB protocol. I'm not sure how to handle server or network interrupts on the client. The application is just a for loop waiting for a message to arrive and the call a go routine to handle that message. Does anybody know a good example how to deal with network or server failures in GO? Or should the application just panic and let the OS create a new instance of the application? The client application will run as a daemon so users can not interact with it.
Asynq
Posts with mentions or reviews of Asynq.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-07-06.
-
Looking for a language agnostic Go task queue with Redis
EDIT : I think the best for my case will be to use the asynq library with a custom js client, it's quite easy to implement (Detailed here)
-
I have a web app that requires allowing users to schedule a recurring task at their own specified time/interval. How would you go about it?
Asynq does this pretty nicely https://github.com/hibiken/asynq/wiki/Periodic-Tasks
-
Examples of using task scheduler with Go?
Asynq looks promising. Never used it myself. https://github.com/hibiken/asynq
-
Recommendation for a selfhosted worker/task queue runner?
Never used it, but it appears to fit most of the criteria. https://github.com/hibiken/asynq
- How to run periodic tasks?
-
What would you rewrite in Golang?
https://github.com/hibiken/asynq is pretty close
-
Suggestions for CRON jobs queue tool
I tried it 2 months ago and it was not suitable for dynamic CRON job enqueue scheduling
-
I’m looking for a suggestion for a queuing library
My current best option is AsynQ (https://github.com/hibiken/asynq but it uses redid and not Postgres for the db
-
What is the best task queue?
Hi, I'm starting a new project that involves distributing task on different (and possibly distributed) workers in Golang. So I'm looking for the best task queue library to use; for now the ones I like are the following (in no particular order): - asynq - machinery - taskq
-
Distributed queue(redis) go
Asynq might do what you need https://github.com/hibiken/asynq
What are some alternatives?
When comparing mangos and Asynq you can also consider the following projects:
NATS - Golang client for NATS, the cloud native messaging system.
machinery - Machinery is an asynchronous task queue/job queue based on distributed message passing.
dbus - Native Go bindings for D-Bus
work - Process background jobs in Go
pubsub - A simple pubsub package for go.
Faktory - Language-agnostic persistent background job server
go-nsq - The official Go package for NSQ
zmq4 - A Go interface to ZeroMQ version 4
temporal - Temporal service
messagebus - Go simple async message bus
nsq - A realtime distributed messaging platform