Designing idempotent job handlers when the database cannot enforce uniqueness
When your ledger table allows historical rows and the unique index is not an option, job keys and outbox patterns still need a story.
Field notes
Guides we wish existed before our last audit—focused on background jobs and concurrent code in production.
Worker pool sizing when CPU is idle but lag keeps climbing
Low CPU with rising queue depth usually means workers are waiting—not that you need more cores.
Three deadlock patterns we see in Go worker pools
Lock ordering mistakes that only show up when shutdown cancels contexts mid-batch.