Rendered at 18:31:45 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
hankbond 1 days ago [-]
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".
bhaney 1 days ago [-]
> 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
advertum 11 hours ago [-]
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?
neoecos 2 days ago [-]
Oban is really awesome, are you inspired by it?
skrebbel 1 days ago [-]
Title said “no overengineering” so I doubt it.
xlii 1 days ago [-]
I would argue that Oban isn't overengineered.
If so should we also consider PostgreSQL overengineered?
It's a shame OP decided to use Elixir as base, many ecosystems don't have mature task queues (e.g. for Rust I had to roll my own: simple_queue) so the space IMO would be more welcoming.
On OTP doubt anything can even make a dent in Oban user base.
gamache 1 days ago [-]
Satisfied former Oban user here. Oban is engineered. Your use-case may be petty, though, like your comment.
abrookewood 2 days ago [-]
Congrats on the launch. Using the Redis protocol was a pretty clever choice. Does it have to run as a stand-alone server?
memset 1 days ago [-]
This is really cool! I built something very similar only I replicated the AWS sqs protocol instead.
I agree that in many areas there often is not much in-between "roll yourself in-memory" and "enterprise grade maxed out scalability focus".
Save yourself the headache of people not reading this and just disable pull requests in the repo settings
If so should we also consider PostgreSQL overengineered?
It's a shame OP decided to use Elixir as base, many ecosystems don't have mature task queues (e.g. for Rust I had to roll my own: simple_queue) so the space IMO would be more welcoming.
On OTP doubt anything can even make a dent in Oban user base.
https://github.com/poundifdef/smoothmq