Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • This is really cool! I built something very similar only I replicated the AWS sqs protocol instead.

    https://github.com/poundifdef/smoothmq

    by memset
  • This is nice. For those wanting to stay on Postgres for DAG type of workflows, check out pgmq based PgFlow: https://github.com/agoodway/pgflow
    by cpursley
  • So lightweight... Using docker and containers. What even is the point.
    by 3dedb728-3f77
  • Congrats on the launch. Using the Redis protocol was a pretty clever choice. Does it have to run as a stand-alone server?
    by abrookewood
  • Using the Redis Streams wire protocol means any existing Redis client works without changes. The queue is stored on disk, so tasks survive a restart. No new client library to add. One question: if a worker stops in the middle of a task, does the message go back to the queue for another worker?
    by advertum
  • Oban is really awesome, are you inspired by it?
    by neoecos
  • > This project is maintained by a single author and pull requests are not accepted

    Save yourself the headache of people not reading this and just disable pull requests in the repo settings

    by bhaney
  • Maybe this says more about me than your project, but I find the use of implementing this with the Redis Streams wire protocol very interesting and creative. Being able to leverage the surface area of existing client SDKs should really help adoption and reduce what you have to maintain in order to widely integrate.

    I agree that in many areas there often is not much in-between "roll yourself in-memory" and "enterprise grade maxed out scalability focus".

    by hankbond

Explore Birbla archives