Celery shine kayan aikin alqaliptar ayyuka na background da gaskiya a cikin Django — aiki wanda bai kamata ya toshe HTTP buƙatun (aika wasiku, sarrafa fayiloli, kira APIs masu jita) ko wanda ke aiki a balle. Ayyuka ana tsada da na yi a asynchronous ta hanyar ayyukan worker da banbanbanta.
():
user = create_user(request.POST)
send_welcome_email(user)
generate_report(user)
redirect()
Yin aiki mai maza inline yana sa masu amfani su jira da kuma yana haɗari na timeout-in buƙatun. Celery tana tufe shi ga ayyukan background don buƙatun ya dawo nan nan.
# tasks.py — define a task
from celery import shared_task
@shared_task
def send_welcome_email(user_id):
user = User.objects.get(id=user_id)
send_email(user.email, "Welcome!") # runs in a WORKER, not the web process
# in a view — QUEUE the task instead of running it inline
def register(request):
user = create_user(request.POST)
send_welcome_email.delay(user.id) # .delay() queues it → returns IMMEDIATELY
return redirect("home") # user gets a fast response
@shared_task decorator yana bayyana task; .delay() (ko .apply_async()) tana tsada shi ga worker don yi asynchronously — view ba ta jira.
Django (web) --.delay()--> BROKER (Redis/RabbitMQ) --> CELERY WORKER (processes the task)
(the message queue) (separate process/machine)
Components:
✓ Broker (Redis or RabbitMQ) — holds the queue of pending tasks
✓ Celery worker(s) — separate processes that pull and execute tasks
✓ Result backend (optional) — stores task results/status
Run workers separately: `celery -A myproject worker`
# run tasks on a schedule (like cron) via Celery Beat
CELERY_BEAT_SCHEDULE = {
"daily-report": {
"task": "myapp.tasks.generate_daily_report",
"schedule": crontab(hour=0, minute=0), # every midnight
},
}
@shared_task(bind=True, max_retries=3, default_retry_delay=60)
def sync_data(self):
try:
do_sync()
except Exception as exc:
raise self.retry(exc=exc) # automatic retries on failure
✓ Retries with backoff (resilience against transient failures)
✓ Task persistence (queued tasks survive restarts via the broker)
✓ Scheduling (Celery Beat — periodic/cron-like tasks)
✓ Rate limiting, concurrency control, task routing/priorities
✓ Workers scale independently of web servers
Sarrafa ayyuka na background tare da Celery shine ilimin da ya zama dole don gina ayyukan Django masu azanci da ake iya tsada, saboda yawancin buƙatun duniya suke buƙatar aiki wanda bai kamata ya faru inline a lokacin buƙatun.
Ganinsuwa yana da mahimmanci saboda matsalar taƙali — tufe aiki mai maza ko jitan (aika wasiku, sarrafa hotuna/fayiloli, samar da rahotanni, kira APIs masu maza, daidaita bayanai) daga lokacin buƙatun-amsawa — yana nan a cikakken ayyuka na aiki.
Yin irin wannan aiki inline yana sa masu amfani su jira, yana haɗari na timeout-in buƙatun, da kuma rasa aiki idan ya gazawarce, yayin da Celery taka wajen bashi masu amfani amsawa nan nan yayin da workers daban-daban suke sarrafa aiki asynchronously da amince.
Bayan asynchronous offloading da sauƙi, Celery tana ba da mahimmancin ikon aiki: ayyuka na tsada/na lokaci-lokaci (ta hanyar Celery Beat, mabaddewa cron don tsara aiki matakin aikace-aikace — rahotanni na yau da gida, ayyukan tsabtawa, ayyuka masu komawa), amsawa ta atomatik da baksed-off (jiya game da kusan ƙasuwar gazawa), tsabar task (ayyuka da aka tsada suna tsira da farawa ta hanyar broker, don aiki ba ya ɓata), da scales daban-daban na workers daga sabar gida.
Ganin tsarin Celery (broker kamar Redis/RabbitMQ da ke riƙe jeri, workers da ke sarrafa ayyuka, sabar sakamakon), yaya za ku bayyana da tsada ayyuka (@shared_task, .delay()), tsada aiki na lokaci-lokaci, da daidaita fasalillar jiya yana da kyakkyawar ilimin senior-level don gina ayyukan Django na aiki wanda ke jima aiki mai maza ko da maza.
Domin sarrafa aiki na background shine buƙatun gida, mahimmanci don ayyukan da ke amsawa, amince — da Celery shine maƙarfin karfinsa a Django ecosystem — karkatar da ita shine dabi'ar, fasalin saniya wanda ke nuna ikon gina ayyukan Django na aiki gida waje daga aiki mai sauƙi-daidai.