Skip to content

Instantly share code, notes, and snippets.

@niczero

niczero/what_we_need_from_a_job_queue.txt

Last active October 12, 2022 14:56
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save niczero/3369773 to your computer and use it in GitHub Desktop.
Save niczero/3369773 to your computer and use it in GitHub Desktop.
Download ZIP
Introduction to Resque
Raw
what_we_need_from_a_job_queue.txt
From https://github.com/blog/542-introducing-resque
We are constantly overloaded and rely very, very heavily on our queue. If it’s
backed up, we need to know why. We need to know if we can fix it. We need
workers to not get stuck and we need to know when they are stuck.
We need to see what the queue is doing. We need to see what jobs have failed.
We need stats: how long are workers living, how many jobs are they processing,
how many jobs have been processed total, how many errors have there been, are
errors being repeated, did a deploy introduce a new one?
We need a background job system as serious as our web framework.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment