neoq
pgmq
neoq | pgmq | |
---|---|---|
5 | 14 | |
244 | 897 | |
- | 13.4% | |
8.3 | 8.9 | |
20 days ago | 24 days ago | |
Go | Rust | |
MIT License | PostgreSQL License |
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
pgmq
- Pgmq: Lightweight message queue extension for Postgres
- Replace SQS / RSMQ with pgmq: A lightweight message queue based on Postgres
-
Introducing pgzx: create PostgreSQL extensions using Zig
And lots of interesting extensions use it, like
https://github.com/tembo-io/pgmq
https://github.com/zombodb/zombodb
https://github.com/supabase/pg_jsonschema
-
Show HN: Hatchet – Open-source distributed task queue
Have you considered https://github.com/tembo-io/pgmq for the queue bit?
- Show HN: An SQS Alternative on Postgres
-
Postgres as Queue
some notes about pgmq, https://github.com/tembo-io/pgmq, that is on this list. It is built as an extension in Postgres, which makes it compatible with all languages that have a Postgres driver.
There's no 'magic' to it, it uses existing Postgres features so all the performance and consistency guarantees of Postgres are to be expected. Easily gets to 10k+ concurrent reads and writes even on smaller sized Postgres instances, which is more than most applications need.
- FLaNK Weekly 31 December 2023
-
What are the best job-scheduling tools, frameworks or libraries?
Newer project but there's no library needed. https://github.com/tembo-io/pgmq. They have a pretty simple SQL api similar to SQS. It's an extension though, so some cloud provider will not support it.
- FLaNK Stack Weekly for 20 Nov 2023
-
Choose Postgres Queue Technology
PGMQ does not require a client library, https://github.com/tembo-io/pgmq so long as your language of choice can run SQL. All the functions live in Postgres, and you just call them with SQL statement. Very similar feel and semantics to SQS.
What are some alternatives?
starqueue
pg-boss - Queueing jobs in Node.js using PostgreSQL like a boss
oban - 💎 Robust job processing in Elixir, backed by modern PostgreSQL and SQLite3
kubeblocks - KubeBlocks is an open-source control plane that runs and manages databases, message queues and other data infrastructure on K8s.
tembo - Monorepo for Tembo Operator, Tembo Stacks, and Tembo CLI
FLaNK-EveryTransitSystem - Every transit system
Asynq - Simple, reliable, and efficient distributed task queue in Go
torchgeo - TorchGeo: datasets, samplers, transforms, and pre-trained models for geospatial data
pgtt - PostgreSQL extension to create, manage and use Oracle-style Global Temporary Tables and the others RDBMS
CML_AMP_Intelligent-QA-Chatbot-with-NiFi-Pinecone-and-Llama2 - The prototype deploys an Application in CML using a Llama2 model from Hugging Face to answer questions augmented with knowledge extracted from the website. This prototype introduces Pinecone as a database for storing vectors for semantic search.
pgjobq - Atomic low latency job queues running on Postgres
screenshot-to-code - Drop in a screenshot and convert it to clean code (HTML/Tailwind/React/Vue)