Django - Celery and Background Tasks
Why is it recommended to use the
@shared_task decorator instead of @app.task in reusable Django apps?Why is it recommended to use the @shared_task decorator instead of @app.task in reusable Django apps?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand difference between @shared_task and @app.task
@shared_task lets tasks be defined without needing the Celery app instance directly.Step 2: Identify why this matters for reusable apps
Reusable apps may not have direct access to the Celery app, so @shared_task is preferred.Final Answer:
Because @shared_task allows the task to be used without direct access to the Celery app instance -> Option DQuick Check:
@shared_task = reusable without app instance [OK]
Quick Trick: @shared_task works without Celery app instance [OK]
Common Mistakes:
MISTAKES- Thinking @app.task is deprecated
- Believing @shared_task runs tasks synchronously
- Assuming @app.task requires models.py
Master "Celery and Background Tasks" in Django
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Django Quizzes