[nightpool]

Nit: the application the author describe doesn't even publish the request using RabbitMQ, as far as I can tell—they publish the request with a simple HTTP request. They use RabbitMQ solely for scheduling the "Check if this task is done yet" job every ~5 minutes. I haven't used RabbitMQ myself, but it does sound like kind of like a square peg / round hole situation to me.

[radicalbyte]

I've built systems similar to this dozens of times and what they're doing makes no sense. Use a database table to store the state of a given job and query it. Super fast, efficient and you're not hiding state in what should be an ephemeral part of your infrastructure.

The MQ is great for scheduling jobs, passing data between different parts of a given process and generally detaching systems. However fast it is not, unless you're using something like Zero MQ for slow IPC.