Asynq VS work

Compare Asynq vs work and see what are their differences.

Asynq

Simple, reliable, and efficient distributed task queue in Go (by hibiken)

work

Process background jobs in Go (by gocraft)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
Asynq work
32 5
8,581 2,315
- 1.0%
7.0 0.0
7 days ago 29 days 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.

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.

work

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

What are some alternatives?

When comparing Asynq and work you can also consider the following projects:

machinery - Machinery is an asynchronous task queue/job queue based on distributed message passing.

Faktory - Language-agnostic persistent background job server

gocelery - Celery Distributed Task Queue in Go

NATS - Golang client for NATS, the cloud native messaging system.

cadence - Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.

temporal - Temporal service

nsq - A realtime distributed messaging platform

rabbit-hole - RabbitMQ HTTP API client in Go