3 ms·
I get the arguments, I think, I just... don't want to be spending any percentage of my time supporting a task queue I've written. I don't want to respond to fea
by pwinnski 4y ago
I get the arguments, I think, I just... don't want to be spending any percentage of my time supporting a task queue I've written. I don't want to respond to feature requests or bug reports or questions. I want to use something that already exists that let the people who developed that thing respond to feature requests and bug reports and questions.
That said, sometimes a task queue isn't the right tool for a job. At my last company, someone built something that could be called a task queue using AWS step functions. What she needed didn't exist, so she built it. Of course, now she has to respond to feature requests, bug reports, and questions about it.
- deleted 4y ago[deleted]
- roflyear 4y agoI don't see how using something that exists gets you out of that problem?
- danpalmer 4y agoThere’s very little maintenance to do when you build what you need. Open source task queues try to solve everyone’s problems and as a result need a lot of work. By only solving your problems you may be surprised at how little code there actually is if you build on top of something like Postgres or Redis.