Downloaded 11 times
![IMPORTANT SETTINGS
• BROKER_URL = 'redis://localhost:6379/0'
• CELERY_RESULT_BACKEND = 'redis://localhost:6379/0'
• CELERY_TASK_RESULT_EXPIRES = 7*86400 # 7 days
• CELERYBEAT_SCHEDULER =
"djcelery.schedulers.DatabaseScheduler"
• CELERY_ACCEPT_CONTENT = ['application/json']
• CELERY_TASK_SERIALIZER = 'json'
• CELERY_RESULT_SERIALIZER = 'json'
• BROKER_BACKEND = "redis"
• BROKER_CONNECTION_TIMEOUT = 5.0
• CELERY_IMPORTS = ('<your-app-name>.tasks',)](https://image.slidesharecdn.com/celery1-170227125910/85/Introduction-to-Django-Celery-and-Supervisor-18-320.jpg)
![IMPORTANT SETTINGS
• BROKER_URL = 'redis://localhost:6379/0'
• CELERY_RESULT_BACKEND = 'redis://localhost:6379/0'
• CELERY_TASK_RESULT_EXPIRES = 7*86400 # 7 days
• CELERYBEAT_SCHEDULER =
"djcelery.schedulers.DatabaseScheduler"
• CELERY_ACCEPT_CONTENT = ['application/json']
• CELERY_TASK_SERIALIZER = 'json'
• CELERY_RESULT_SERIALIZER = 'json'
• BROKER_BACKEND = "redis"
• BROKER_CONNECTION_TIMEOUT = 5.0
• CELERY_IMPORTS = ('<your-app-name>.tasks',)](https://image.slidesharecdn.com/celery1-170227125910/75/Introduction-to-Django-Celery-and-Supervisor-18-2048.jpg)
More Related Content
Similar to Introduction to Django-Celery and Supervisor
Introduction to Django-Celery and Supervisor
- 1.
- 2. What is Celery? “Celeryis an asynchronous task queue based on distributed message passing.” It is a powerful, production-ready asynchronous job queue, which allows you to run time-consuming Python functions in the background.
- 3. Why should Iuse Celery?
- 4. User perspective • Minimizerequest/response cycle • Smoother user experience • Difference between pleasant and unpleasant
- 5. Developer perspective • Offloadtime/cpu intensive processes • Scalability - add workers as needed • Flexibility - many points of customization • Actively developed • Great documentation • Lots of tutorials
- 6. OUT OF THE REQUEST/RESPONSE CYCLE •Example: Sending emails asynchronously.
- 7. TASKS IN THE BACKGROUND. •Example: Computational heavy jobs. • Example: Interacting with external APIs.
- 8.
- 10.
- 11. PRODUCER • Produces atask for the queue.
- 12. BROKER • Stores thetask backlog • Answers, what work remains to be done? • RabbitMQ, Redis, SQLAlchemy, Django's ORM, MongoDB
- 13. WORKER • Execute andconsumes tasks. • Distributed.
- 14. RESULTS BACKEND • Storesthe results from our tasks.
- 15.
- 16.
- 17.
- 18. IMPORTANT SETTINGS • BROKER_URL= 'redis://localhost:6379/0' • CELERY_RESULT_BACKEND = 'redis://localhost:6379/0' • CELERY_TASK_RESULT_EXPIRES = 7*86400 # 7 days • CELERYBEAT_SCHEDULER = "djcelery.schedulers.DatabaseScheduler" • CELERY_ACCEPT_CONTENT = ['application/json'] • CELERY_TASK_SERIALIZER = 'json' • CELERY_RESULT_SERIALIZER = 'json' • BROKER_BACKEND = "redis" • BROKER_CONNECTION_TIMEOUT = 5.0 • CELERY_IMPORTS = ('<your-app-name>.tasks',)
- 19. Write code incelery.py
- 20. Intialize celery in__init__.py
- 21.
- 22. NEVER PASS OBJECTSAS ARGUMENTS.
- 23.
- 25.
- 26.
- 27.
- 28.