interoperability can also be achieved exposing an HTTP endpoint and having a task that requests it (web- hooks). What do I need? Version Requirements Celery version 4.0 runs on • Python 2.7, 3.4, 3.5 • PyPy aren’t strictly necessary, but they can make development easier, and sometimes they add important hooks like closing database connections at fork(2). Quick Jump I want to • get the return value of a available in Django 1.9 and above, if you are using a version prior to that then the django- transaction-hooks library adds support for this. Example Let’s take a real world example: a blog where comments posted

aren’t strictly necessary, but they can make development easier, and sometimes they add important hooks like closing database connections at fork(2). Quick Jump I want to ⟶ get the return value of a above, if you are using a version prior to that then the django-transaction-hooks [https://github.com/carljm/django-transaction-hooks] library adds support for this. Example Let’s take a real world example: Bootsteps is a technique to add functionality to the workers. A bootstep is a custom class that defines hooks to do custom actions at different stages in the worker. Every bootstep belongs to a blueprint, and

ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, AMQP (high performance). Web- hooks Your tasks can also be HTTP callbacks, enabling cross-language communication. Rate limiting Supports

interoperability can also be achieved exposing an HTTP endpoint and having a task that requests it (web- hooks). What do I need? Version Requirements Celery version 4.0 runs on • Python 2.7, 3.4, 3.5 • PyPy aren’t strictly necessary, but they can make development easier, and sometimes they add important hooks like closing database connections at fork(2). Quick Jump I want to • get the return value of a available in Django 1.9 and above, if you are using a version prior to that then the django- transaction-hooks library adds support for this. Example Let’s take a real world example: a blog where comments posted

aren’t strictly necessary, but they can make development easier, and sometimes they add important hooks like closing database connections at fork(2). Quick Jump I want to ⟶ get the return value of a above, if you are using a version prior to that then the django-transaction-hooks [https://github.com/carljm/django-transaction-hooks] library adds support for this. Example Let’s take a real world example: Bootsteps is a technique to add functionality to the workers. A bootstep is a custom class that defines hooks to do custom actions at different stages in the worker. Every bootstep belongs to a blueprint, and

aren’t strictly necessary, but they can make development easier, and sometimes they add important hooks like closing database connections at fork(2). Quick Jump I want to ⟶ get the return value of a above, if you are using a version prior to that then the django-transaction-hooks [https://github.com/carljm/django-transaction-hooks] library adds support for this. Example Let’s take a real world example: Bootsteps is a technique to add functionality to the workers. A bootstep is a custom class that defines hooks to do custom actions at different stages in the worker. Every bootstep belongs to a blueprint, and

interoperability can also be achieved exposing an HTTP endpoint and having a task that requests it (web- hooks). What do I need? Version Requirements Celery version 4.0 runs on • Python 2.7, 3.4, 3.5 • PyPy aren’t strictly necessary, but they can make development easier, and sometimes they add important hooks like closing database connections at fork(2). Quick Jump I want to • get the return value of a available in Django 1.9 and above, if you are using a version prior to that then the django- transaction-hooks library adds support for this. Example Let’s take a real world example: a blog where comments posted

interoperability can also be achieved exposing an HTTP endpoint and having a task that requests it (web- hooks). What do I need? Version Requirements Celery version 4.0 runs on • Python 2.7, 3.4, 3.5 • PyPy aren’t strictly necessary, but they can make development easier, and sometimes they add important hooks like closing database connections at fork(2). Quick Jump I want to • get the return value of a available in Django 1.9 and above, if you are using a version prior to that then the django- transaction-hooks library adds support for this. Example Let’s take a real world example: a blog where comments posted

aren’t strictly necessary, but they can make development easier, and sometimes they add important hooks like closing database connections at fork(2). Quick Jump I want to ⟶ get the return value of a above, if you are using a version prior to that then the django-transaction-hooks [https://github.com/carljm/django-transaction-hooks] library adds support for this. Example Let’s take a real world example: Bootsteps is a technique to add functionality to the workers. A bootstep is a custom class that defines hooks to do custom actions at different stages in the worker. Every bootstep belongs to a blueprint, and

aren’t strictly necessary, but they can make development easier, and sometimes they add important hooks like closing database connections at fork(2). Quick Jump I want to ⟶ get the return value of a above, if you are using a version prior to that then the django-transaction-hooks [https://github.com/carljm/django-transaction-hooks] library adds support for this. Example Let’s take a real world example: Bootsteps is a technique to add functionality to the workers. A bootstep is a custom class that defines hooks to do custom actions at different stages in the worker. Every bootstep belongs to a blueprint, and