broadcast messaging. A range of built-in commands exist in addition to the ability to easily define your own. (AMQP/Redis only) Moni- toring You can capture everything happening with the workers in real-time SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. For this example we will use the amqp result backend, which sends states as messages. The backend SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. No backend works well for every use case. You should read about the strengths and weaknesses of each

broadcast messaging. A range of built-in commands exist in addition to the ability to easily define your own. (AMQP/Redis only) Moni- toring You can capture everything happening with the workers in real-time SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. For this example we will use the amqp result backend, which sends states as messages. The backend SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. No backend works well for every use case. You should read about the strengths and weaknesses of each

broadcast messaging. A range of built-in commands exist in addition to the ability to easily define your own. (AMQP/Redis only) Moni- toring You can capture everything happening with the workers in real-time SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. There is no backend that works well for every single use case, but for historical reasons the default read about the strenghts and weaknesses of each backend, and choose the most appro- priate for your own needs. See also: Task result backend settings AMQP Result Backend The AMQP result backend is special

broadcast messaging. A range of built-in commands exist in addition to the ability to easily define your own. (AMQP/Redis only) Monitoring You can capture everything happening with the workers in real-time SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. For this example we will use the amqp result backend, which sends states as messages. The backend SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. No backend works well for every use case. You should read about the strengths and weaknesses of each

the applications listed in INSTALLED_APPS. If you want to do something special you can create your own loader to do what you want. The entity responsible for registering your task in the registry is a this for each task. There is built-in support for using pickle, JSON and YAML, and you can add your own custom serializers by registering them into the carrot serializer registry. The default serializer powerful machines, while low priority tasks are sent to dedicated machines that can handle these at their own pace. For the sake of example we have only one exchange called tasks. There are different types of

broadcast messaging. A range of built-in commands exist in addition to the ability to easily define your own. (AMQP/Redis only) Monitoring You can capture everything happening with the workers in real-time SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. For this example we will use the amqp result backend, which sends states as messages. The backend SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. No backend works well for every use case. You should read about the strengths and weaknesses of each

the applications listed in INSTALLED_APPS. If you want to do something special you can create your own loader to do what you want. The entity responsible for registering your task in the registry is a this for each task. There is built-in support for using pickle, JSON and YAML, and you can add your own custom serializers by registering them into the carrot serializer registry. The default serializer powerful machines, while low priority tasks are sent to dedicated machines that can handle these at their own pace. For the sake of example we have only one exchange called tasks. There are different types of

broadcast messaging. A range of built-in commands exist in addition to the ability to easily define your own. (AMQP/Redis only) Monitoring You can capture everything happening with the workers in real-time SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. There is no backend that works well for every single use case, but for historical reasons the default read about the strenghts and weaknesses of each backend, and choose the most appropriate for your own needs. See also Task result backend settings AMQP Result Backend The AMQP result backend is special

broadcast messaging. A range of built-in commands exist in addition to the ability to easily define your own. (AMQP/Redis only) Moni- toring You can capture everything happening with the workers in real-time SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. For this example we will use the amqp result backend, which sends states as messages. The backend SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. No backend works well for every use case. You should read about the strengths and weaknesses of each

broadcast messaging. A range of built-in commands exist in addition to the ability to easily define your own. (AMQP/Redis only) Monitoring You can capture everything happening with the workers in real-time SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. For this example we will use the amqp result backend, which sends states as messages. The backend SQLAlchemy/Django ORM, Memcached, Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. No backend works well for every use case. You should read about the strengths and weaknesses of each