neoq

Queue-agnostic background job library for Go, with a pleasant API and powerful features. (by acaloiaro)

Neoq Alternatives

Similar projects and alternatives to neoq

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better neoq alternative or higher similarity.

neoq reviews and mentions

Posts with mentions or reviews of neoq. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-24.
  • 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 - Onboard AI
    app.getonboardai.com | 22 Feb 2024
    Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at app.getonboardai.com. Learn more →

Stats

Basic neoq repo stats
4
226
8.7
6 days ago

acaloiaro/neoq is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of neoq is Go.

Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com