The easiest answer I could give is that django signals are like hooks. Something you wish to preform AFTER or BEFORE some model action. Like you wish to adjust account balance on model save. Than you would use post_save builtin django signal.
Celery is here to handle task in background. Like you wish to process some sort of upload but you want to queue it up against some broker such as rabbitmq, redis, etc. On this way you can optimize stuff and return back user faster response saying "hey, process is backgrounded. Will notify you once it's completed". Than when task finishes you can call callback and let user know as example. Consider this. You have 100000 users uploading video. That video would go into celery task so that you can scale it up properly and distribute against network + make UX appropriate. Hope this makes sense. All best, Nevio -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAD1DFf1nLW4GnBCBdNKnLmu22kB79-q8xf7JmMbVVkaidbCnhg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
