Neoq Alternatives

neoq reviews and mentions

• Do you need Redis? PostgreSQL does queuing, locking, and pub/sub
  12 projects | news.ycombinator.com | 3 Nov 2024

  https://github.com/acaloiaro/neoq (Go)

• Show HN: Hatchet – Open-source distributed task queue
  22 projects | news.ycombinator.com | 8 Mar 2024
• Choose Postgres Queue Technology
  17 projects | news.ycombinator.com | 24 Sep 2023

  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
  68 projects | news.ycombinator.com | 16 Aug 2023

  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?
  8 projects | /r/golang | 3 Jun 2023

  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
  16 projects | news.ycombinator.com | 11 Apr 2023

  This is exactly the thesis behind neoq: https://github.com/acaloiaro/neoq

• A note from our sponsor - SaaSHub
  www.saashub.com | 20 May 2025

  SaaSHub helps you find the best software and product alternatives Learn more →