Keep the job queue in Postgres

Retries and tracking jobs in a regular old SQL database is actually pretty easy, and I prefer that to managing another complex system.

Seriously, every second month someone wanted to add a job queue to their system. I knocked it back and everyone just used Postgres. It would've been a nightmare having to debug state issues between the database, the app server and the message queue.

A job queue seems good at the beginning, but it really comes back to bite you later.