Why did you use Redis+Celery instead of RabbitMQ?

Choosing Redis+Celery instead of RabbitMQ is often due to the following reasons:

• Ease of setup and use: Redis is easier to deploy and configure, especially for small projects or prototypes.
• Celery natively supports Redis as a broker: Celery is tightly integrated with Redis, simplifying task and queue management.
• High performance of Redis: Redis is an in-memory store, which provides very fast message processing.
• Additional capabilities of Redis: Besides being a message broker, Redis can be used for caching, storing task states, and other purposes.

RabbitMQ is a full-fledged message broker supporting complex routing scenarios, acknowledgments, and transactions, but it requires more complex setup and administration.

Thus, choosing Redis+Celery can be justified if simplicity, speed, and Python integration are important, and complex routing scenarios are not required.