<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Job Queues on App Coding</title>
    <link>https://appcoding.com/tags/job-queues/</link>
    <description>Recent content in Job Queues on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/job-queues/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Background Job Queue in One SQLite File Covers What Most Apps Deploy Redis For</title>
      <link>https://appcoding.com/a-background-job-queue-in-one-sqlite-file-covers-what-most-apps-deploy-redis-for/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/a-background-job-queue-in-one-sqlite-file-covers-what-most-apps-deploy-redis-for/</guid>
      <description>&lt;p&gt;A signup handler has to send a welcome email, and sending it inline puts a third-party API call inside your request. So you move it into a background job, and the usual next step is Redis, a client library, a worker process, a dashboard, and a note in the deploy docs about what happens to queued jobs when Redis restarts without persistence. If the app runs on one machine, you&amp;rsquo;ve added a second stateful service to look after a table&amp;rsquo;s worth of data.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
