vintasoftware/celery-tasks-checklist

Useful checklist for building great Celery tasks.

Celery Tasks Checklist

Adding a New Language:

• To add a new language you will need to create another markdown file containing the new acronym language:
  • E.g. checklist-pt.md.
• No further approval will be necessary;
• The new checklist language should be visible on Devckecklists after you saved the file on your repository.

Important Notes:

• Markdown is the only way to write checklists on Devchecklists;
• For tips about how to use markdown to write checklists, please take a look at these raw files:
  • checklist-en.md sample markdown;
  • README.md contained on this repository;
  • Another checklists markdowns from Devchecklists.
• Changes on the checklist repository will reflect on the current checklist of Devchecklists.

Commercial Support

This project, as other Vinta open-source projects, is used in products of Vinta clients. We are always looking for exciting work, so if you need any commercial support, feel free to get in touch: [email protected]

Copyright (c) 2018 Vinta Serviços e Soluções Tecnológicas Ltda. MIT License

celery-tasks-checklist's Issues

Talk about being careful on updating task kwargs

Since you may have tasks running and/or due to retry with old kwargs

Check tasks will be automatically picked up in case of outage

In case of outage make sure Celery will pick up the tasks that were supposed to run while the system was off (if this makes sense in your business logic).

Bad:

# Messages for some tasks won't be sent if the outage lasts one day
for task in Tasks.objects.filter(due_to=today):
    send_messages()

Better:

for task in Tasks.objects.filter(due_to__lte=today, sent=False):
   send_messages()

Talk about `autoretry_for` and `retry_backoff`

http://docs.celeryproject.org/en/master/userguide/tasks.html#automatic-retry-for-known-exceptions

celery/celery#4101

Link on footer pointing to wrong repo

https://github.com/vintasoftware/celery-tasks-checklist/blob/master/index.html#L170

please fix it asap.

Thanks

Talk about `on_commit` if using transactions or ATOMIC_REQUESTS

Link to: https://www.vinta.com.br/blog/2016/database-concurrency-in-django-the-right-way/