<?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 Kuldeep Pisda</title><link>https://kdpisda.in/tag/background-jobs/</link><description>Recent content in Background-Jobs on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 28 Feb 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/background-jobs/index.xml" rel="self" type="application/rss+xml"/><item><title>Payments Never Wait Behind a Transcode</title><link>https://kdpisda.in/queue-per-workload-celery-rabbitmq/</link><pubDate>Sat, 28 Feb 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/queue-per-workload-celery-rabbitmq/</guid><description>&lt;p&gt;The last chapter ended on a loose thread I promised to pick up: inside the one Django hub, plenty of work has no business running inside a web request. Sending a donor&amp;rsquo;s receipt, fanning out a notification, kicking off a video transcode — those all get handed off to Celery. And the moment you have both a two-hour transcode and a receipt a human is actively refreshing their inbox for, &lt;em&gt;how&lt;/em&gt; you queue them stops being a detail and becomes the thing that decides whether the platform feels instant or broken.&lt;/p&gt;</description></item></channel></rss>