# Ansible as alternative to celery or python-rq?

**URL:** <https://forum.ansible.com/t/ansible-as-alternative-to-celery-or-python-rq/22186>\
**Category:** Ansible Project\
**Created:** [August 2, 2016, 7:19am UTC](https://forum.ansible.com/t/ansible-as-alternative-to-celery-or-python-rq/22186 "2016-08-02T07:19:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas\_Guttler](https://avatars.discourse-cdn.com/v4/letter/t/9f8e36/32.png) [@Thomas\_Guttler](https://forum.ansible.com/u/Thomas_Guttler)\
**Post date:** [August 2, 2016, 7:19am UTC](https://forum.ansible.com/t/ansible-as-alternative-to-celery-or-python-rq/22186/1 "2016-08-02T07:19:03Z")

</div>

Hi,

we need to implement a use case which looks like celery or python-rq could be used.

We already use ansible in this context.

I ask myself if it is good to have two systems for queueing jobs and processing them in the background.  
We already have ansible. Add another (celery or python-rq) or use ansible for this?

Can you understand what I ask? If not, please tell me.

I have some guidelines which conflict here:

- less is more
- do re-use
- go common routes.

What do you think?