Hacker News new | past | comments | ask | show | jobs | submit login

Looks like they needed to have built-in support for time based scheduled execution of jobs at a specific time in the future. Rabbit MQ does not have that (that I'm aware of) without doing some horrible hacks around one queue per message.



ActiveMQ's had that for a couple of versions though. Another highly performant/available, atomic, consistent, durable and mature queueing server.


Correct. Celery's implementation dequeues but doesn't acknowledge the task, holding it until the timer is reached.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: