<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Faktory on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/faktory/</link>
    <description>Recent content in Faktory on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 28 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/faktory/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Ruby Background Job Processors: Sidekiq vs Shoryuken vs Faktory vs Sucker Punch Comparison</title>
      <link>https://www.pistack.xyz/posts/2026-07-28-ruby-background-job-processors-sidekiq-shoryuken-faktory-sucker-punch-comparison/</link>
      <pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-28-ruby-background-job-processors-sidekiq-shoryuken-faktory-sucker-punch-comparison/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Background job processing is essential for any production Ruby application. Whether you need to send emails, generate reports, resize images, or process webhooks — pushing these tasks to a background worker keeps your web server responsive and your users happy. The Ruby ecosystem has a rich tradition of background job libraries, each with different tradeoffs in architecture, scalability, and operational complexity.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
