Closed alp82 closed 12 years ago
Pretty certain that Celery can do everything this can do and more.
The only real reason to use it would be it's simple. When I started writing this Celery seemed overkill for what I needed. Most of the documentation/tutorials for Celery talked about using ampq or similar, which would have been too much to run on my shared web host. Ruby had delayed job and that seemed a better fit for what I wanted.
It seems though that Celery now is probably the best bet for most people and can be run with a database backend.
I think the only extra feature that background task has, is the ability to re-schedule tasks automatically when an identical task is submitted.
I am just curious if this has anything Celery can't do. Are there major differences?