> They should have used RabbitMQ just to kick off the job, immediately ACKing the request, and job tracking/completion handled inside... a database. That's wha

> They should have used RabbitMQ just to kick off the job, immediately ACKing the request, and job tracking/completion handled inside... a database. That's what I think too. Use the message queue for communication and potentially work distribution and the database for the rest like internal state.