A Practical Guide to Background Jobs

Abstract code gradient artwork

We measured first, and the bottleneck was not where anyone expected. If the error message does not say what to do next, it is half an error message. Feature flags are debt with an expiration date you must actually enforce.

Details

Logs answer questions you knew to ask; traces answer the ones you did not. We wrote the migration twice: once to learn, once to ship. The fastest query is the one you never send, but the second fastest has a good index.

Caches are easy to add and surprisingly hard to remove. Our on-call rotation improved the day we deleted half of the alerts.

Going further

Small pull requests get real reviews, large ones get approvals. The best architecture diagram is the one the new hire can redraw from memory. Latency percentiles tell a story that averages politely hide. Caches are easy to add and surprisingly hard to remove.

  • Alert on symptoms, not causes
  • Measure p95 and p99, not just the mean
  • Pin versions, update on purpose
  • Keep migrations reversible

Most production incidents start as a small assumption nobody wrote down. Security is mostly about saying no to defaults that were convenient in 2010.

Getting started

We measured first, and the bottleneck was not where anyone expected. Small pull requests get real reviews, large ones get approvals. Latency percentiles tell a story that averages politely hide. Security is mostly about saying no to defaults that were convenient in 2010.

We wrote the migration twice: once to learn, once to ship. Latency percentiles tell a story that averages politely hide.

The fastest query is the one you never send, but the second fastest has a good index. Naming things well saved us more time than any framework migration.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *