<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Background-Processing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/background-processing/</link>
    <description>Recent content in Background-Processing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/background-processing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>JobRunr vs ShedLock vs db-scheduler in 2026: How to Run Background Jobs in Java Without Duplicates</title>
      <link>https://www.pistack.xyz/posts/2026-09-18-java-background-job-scheduling-jobrunr-shedlock-db-scheduler/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-18-java-background-job-scheduling-jobrunr-shedlock-db-scheduler/</guid>
      <description>&lt;p&gt;You scale your Spring Boot service from one instance to four, and suddenly every &lt;code&gt;@Scheduled&lt;/code&gt; method fires four times: four invoices emailed, four reports generated, four webhooks delivered. The instinct is to reach for a distributed lock — but &lt;strong&gt;ShedLock, JobRunr, and db-scheduler solve three genuinely different problems&lt;/strong&gt;, and treating them as interchangeable is why teams end up with duplicated side effects or silently skipped jobs after a restart.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Oban vs Broadway vs Quantum in 2026: Which Elixir Background Processing Layer Should You Use?</title>
      <link>https://www.pistack.xyz/posts/2026-09-18-elixir-background-processing-oban-broadway-quantum/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-18-elixir-background-processing-oban-broadway-quantum/</guid>
      <description>&lt;p&gt;Elixir makes concurrency so cheap that teams quietly accumulate &lt;code&gt;Task.start/1&lt;/code&gt; calls all over their codebase — until the first deploy kills 4,000 in-flight jobs mid-execution and nobody can say which emails went out. The BEAM gives you lightweight processes for free, but &lt;strong&gt;durability, retries, and back-pressure are not free&lt;/strong&gt;, and those are exactly the three things that separate Elixir&amp;rsquo;s background processing libraries.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
