<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Message Queues on Nalar</title>
    <link>https://nalar.dev/tags/message-queues/</link>
    <description>Recent content in Message Queues on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/message-queues/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Design Dead-Letter Queues for Poison Messages</title>
      <link>https://nalar.dev/design-dead-letter-queues-for-poison-messages/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/design-dead-letter-queues-for-poison-messages/</guid>
      <description>&lt;p&gt;Retries are useful when a failure is temporary. A database may be unavailable for a few seconds, a downstream service may return an overload response, or a network connection may disappear and recover.&lt;/p&gt;&#xA;&lt;p&gt;Retries become harmful when the message itself cannot succeed.&lt;/p&gt;&#xA;&lt;p&gt;A malformed payload, an unsupported schema version, a reference to permanently missing data, or a deterministic application bug can make the same message fail on every delivery. If the broker keeps returning that message to consumers indefinitely, the system spends capacity repeating work that has no chance of succeeding.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
