Celery is typically used with RabbitMQ, which is an advanced message broker.
If you don't need the complexity (most don't), need persistence, transactional guarantees and already have PostgreSQL in your stack, then the pq-library is probably a good option.
It's not really for a distributed setup, but meant to operate within a cluster (local area network, same data center). Most people don't have distributed systems ;-).
Comments
I wrote https://pypi.python.org/pypi/pq, a transactional task queue for PostgreSQL, depends only on psycopg2.
It does about 1000 ops per second, depending on your database configuration, network etc.
That's pretty cool. What are the benefits of using this over celery?
Celery is typically used with RabbitMQ, which is an advanced message broker.
If you don't need the complexity (most don't), need persistence, transactional guarantees and already have PostgreSQL in your stack, then the pq-library is probably a good option.
It's not really for a distributed setup, but meant to operate within a cluster (local area network, same data center). Most people don't have distributed systems ;-).