neoq
Asynq
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.
neoq
- Show HN: Hatchet – Open-source distributed task queue
-
Choose Postgres Queue Technology
I just want to commend OP - if they’re here - for choosing an int64 for job IDs, and MD5 for hashing the payload in Neoq, the job library linked [0] from the article.
Especially given the emphasis on YAGNI, you don’t need a UUID primary key, and all of its problems they bring for B+trees (that thing RDBMS is built on), nor do you need the collision resistance of SHA256 - the odds of you creating a dupe job hash with MD5 are vanishingly small.
As to the actual topic, it’s fine IFF you carefully monitor for accumulating dead tuples, and adjust auto-vacuum for that table as necessary. While not something you’d run into at the start, at a modest scale you may start to see issues. May. You may also opt to switch to Redis or something else before that point anyway.
[0]: https://github.com/acaloiaro/neoq
-
Ask HN: Tell us about your project that's not done yet but you want feedback on
Neoq (https://github.com/acaloiaro/neoq) is a background job processor for Go.
Yes, another one. It began from my desire to have a robust Postgres-backed job processor. What I quickly realized was that the interface in front of the queue was what was really important. This allowed me to add both in-memory and Redis (provided by asynq) backends behind the same interface. Which allows dependent projects to switch between different backends in different settings/durable requirements. E.g. in-memory for testing/development, postgres when you're not running Google-scale jobs, and Redis for all the obvious use cases for a Redis-backed queue.
This allows me to swap out job queue backends without changing a line of job processor code.
I'm familiar with the theory that one shouldn't implement queues on Postgres, and to a large extent, I disagree with those theories. I'm confident you can point out a scenario in which one shouldn't, and I contend that those scenarios are the exception rather than the rule.
-
Examples of using task scheduler with Go?
I created a background processor called Neoq (https://github.com/acaloiaro/neoq) that is likely to interest you.
-
SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue
This is exactly the thesis behind neoq: https://github.com/acaloiaro/neoq
Asynq
-
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?
starqueue
machinery - Machinery is an asynchronous task queue/job queue based on distributed message passing.
oban - 💎 Robust job processing in Elixir, backed by modern PostgreSQL and SQLite3
work - Process background jobs in Go
tembo - Monorepo for Tembo Operator, Tembo Stacks, and Tembo CLI
Faktory - Language-agnostic persistent background job server
pgtt - PostgreSQL extension to create, manage and use Oracle-style Global Temporary Tables and the others RDBMS
NATS - Golang client for NATS, the cloud native messaging system.
pgjobq - Atomic low latency job queues running on Postgres
temporal - Temporal service
starlark-go - Starlark in Go: the Starlark configuration language, implemented in Go
nsq - A realtime distributed messaging platform