65 points by ent1c3d 3 days ago | 10 comments
- 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".
- > 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
- This is really cool! I built something very similar only I replicated the AWS sqs protocol instead.
- Oban is really awesome, are you inspired by it?
- Title said “no overengineering” so I doubt it.
- 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.
- Satisfied former Oban user here. Oban is engineered. Your use-case may be petty, though, like your comment.
- Congrats on the launch. Using the Redis protocol was a pretty clever choice. Does it have to run as a stand-alone server?
- 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
- [flagged]
- [flagged]
- good