<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Operations on Company Engineering</title><link>https://company-engineering.pages.dev/tags/operations/</link><description>Recent content in Operations on Company Engineering</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 05 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://company-engineering.pages.dev/tags/operations/index.xml" rel="self" type="application/rss+xml"/><item><title>What We Learned From Running Background Workers in Production</title><link>https://company-engineering.pages.dev/posts/what-we-learned-from-running-background-workers-in-production/</link><pubDate>Fri, 05 Jun 2026 00:00:00 +0000</pubDate><guid>https://company-engineering.pages.dev/posts/what-we-learned-from-running-background-workers-in-production/</guid><description>&lt;p&gt;Background workers are where a lot of our most important work happens — sending
notifications, generating exports, syncing data, billing. They&amp;rsquo;re also where the
most surprising production incidents start. Here&amp;rsquo;s what running them at scale has
taught us.&lt;/p&gt;
&lt;h2 id="jobs-are-not-functions"&gt;Jobs are not functions&lt;/h2&gt;
&lt;p&gt;A function call either returns or throws. A background job can also be retried,
duplicated, delayed for hours, killed mid-execution, or run on code that has
since been deployed over. Designing jobs means designing for all of those states,
not just success and failure.&lt;/p&gt;</description></item></channel></rss>