5 ms·
I'm not sure I quite follow this statement: > In the list above, I skipped things similar to pub/sub servers called "job queues" - they only let one "subscribe
by stephenr 7y ago
I'm not sure I quite follow this statement:
> In the list above, I skipped things similar to pub/sub servers called "job queues" - they only let one "subscriber" watch for new "events" at a time, and keep a queue of unprocessed events:
If your job queue only allows one single worker (even per named queue), I'd argue it's a shit job queue.
- ibejoeb 7y agoThe article mentions Celery and Gearman. I'm not here to defend celery generally, but it has no such limitation.
- ergo14 7y agoYeah, we are running about 400 celery processes over 30 queues and at this point I think I would have noticed :)
- stephenr 7y agoRight, I spent some time earlier this year researching a number of job queue systems for a client and never came across one that had this limitation, which kind of makes me wonder what exactly the article is trying to claim.