<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Service-Bus on Joshua Antony | Tech Blog</title><link>https://blogs.joshuaantony.com/tags/service-bus/</link><description>Recent content in Service-Bus on Joshua Antony | Tech Blog</description><generator>Hugo</generator><language>en-us</language><copyright>2026 Joshua Antony · Tech Blog</copyright><lastBuildDate>Sun, 01 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blogs.joshuaantony.com/tags/service-bus/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Queue's Throughput Is Your Slowest Dependency — and 'Retry in 5 Minutes' Can Take an Hour</title><link>https://blogs.joshuaantony.com/posts/throughput-is-the-slowest-dependency/</link><pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate><guid>https://blogs.joshuaantony.com/posts/throughput-is-the-slowest-dependency/</guid><description>A fast consumer in front of a slow API drains at the API&amp;rsquo;s speed. Capping concurrency protected the dependency, but a delayed retry on a deep queue is only as delayed as the backlog ahead of it.</description></item><item><title>Service Bus Prefetch Locks Messages You Aren't Processing — and Your Backoff Clock Might Be Wrong</title><link>https://blogs.joshuaantony.com/posts/service-bus-prefetch-and-retry-backoff/</link><pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate><guid>https://blogs.joshuaantony.com/posts/service-bus-prefetch-and-retry-backoff/</guid><description>Prefetch starts the lock clock before your code sees the message, and &amp;lsquo;retry in 5 minutes&amp;rsquo; computed from the enqueue time can land hours in the past. Two small details that wrecked a retry budget.</description></item><item><title>Service Bus Lock Expiry Quietly Creates Duplicate Messages — and a Transaction Fixes the Retry Path</title><link>https://blogs.joshuaantony.com/posts/service-bus-lock-loss-duplicate-messages/</link><pubDate>Thu, 29 Oct 2026 00:00:00 +0000</pubDate><guid>https://blogs.joshuaantony.com/posts/service-bus-lock-loss-duplicate-messages/</guid><description>When a lock expires mid-processing, &amp;lsquo;schedule a retry, then complete the original&amp;rsquo; leaves two live copies of one message. Doing both in one Service Bus transaction brings it back to exactly one.</description></item></channel></rss>