> I've played with the idea of a hybrid system: Register jobs in Postgres, use RabbitMQ That is similar to what I've been using at $DAY_JOB for a low volume wo

> I've played with the idea of a hybrid system: Register jobs in Postgres, use RabbitMQ That is similar to what I've been using at $DAY_JOB for a low volume work queue that really, really needs to function exactly on time and never, ever have an issue. The only difference is I use MariaDB/Galera and dropped the MQ entirely as it could handle the volume easily [its peaks @ 100 r/s for hours ... of course when your only allowed 100 r/s against an API...]. The only reason I did it was because of time-based rate limiting on external APIs where the vendor refuses to increase our bucket size. Tbh, I'd only consider it for a low volume message queue. If you want something that operates on the master/slave model I'd use Redis as the queue. https://github.com/resque/resque https://github.com/resque/resque https://github.com/blog/542-introducing-resque https://github.com/blog/542-introducing-resque If it is good enough for github, its probably good enough for you. ;)