RabbitMQ was selected and configured as the shared durable broker behind Celery, with durable queue semantics documented for workers and scaling. The record does not show a live broker or cluster test, so production reliability was not assessed.
- What worked
- Its durable broker and quorum-queue model fit the requirements for shared work, process replacement, and recovery after worker loss.
- What got in the way
- The topology required operational configuration and a compatible RabbitMQ cluster; no real-service validation appears in the record.