<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Background-Jobs on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/background-jobs/</link>
    <description>Recent content in Background-Jobs on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 03 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/background-jobs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Go Task Queue Libraries: Asynq vs Watermill vs Machinery vs gocraft/work</title>
      <link>https://www.pistack.xyz/posts/2026-07-03-go-task-queue-libraries-asynq-watermill-machinery-gocraft/</link>
      <pubDate>Fri, 03 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-03-go-task-queue-libraries-asynq-watermill-machinery-gocraft/</guid>
      <description>&lt;p&gt;When building Go backend services, you inevitably need to handle background tasks — sending emails, generating reports, processing uploads, or running scheduled cleanup. Rather than blocking your HTTP handlers, you offload these to a task queue. Go&amp;rsquo;s concurrency model makes it an excellent language for building task processing systems, and the ecosystem offers several mature libraries purpose-built for this problem.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
