Making Sure Jobs Succeed…Eventually
We write code to solve a problem or achieve some result. When that code is split up such that some of it runs while a user is waiting and some runs in a background job, it’s hard to clearly understand what code ran by looking at the server logs. For example, if your users are successfully creating orders, but none of the CompleteOrderJob jobs are completing, you have a problem.
The biggest challenge in managing a system with Sidekiq jobs is making sure that the jobs all eventually complete. This requires knowing what jobs have failed, why they failed, and fixing anything needed to make them succeed when retried. For even a moderately sized system, this can be an overwhelming task, at least without some sort ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access