<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Webhooks on ukue.com</title>
    <link>https://ukue.com/tags/webhooks/</link>
    <description>Recent content in Webhooks on ukue.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 06 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ukue.com/tags/webhooks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Webhook Delivery With ukue: A Day of Retries, Then Dead Letters Instead of Lost Events</title>
      <link>https://ukue.com/webhook-delivery-with-ukue-a-day-of-retries-then-dead-letters-instead-of-lost-events/</link>
      <pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://ukue.com/webhook-delivery-with-ukue-a-day-of-retries-then-dead-letters-instead-of-lost-events/</guid>
      <description>&lt;p&gt;Say a small company runs an invoicing service written in Go. Its customers want to hear about payments the moment they happen, so the service sends webhooks: an HTTP POST with the event to a URL each customer chooses. Those URLs point at servers the company doesn&amp;rsquo;t control. They go down for maintenance, get redeployed, hit rate limits and return errors. If the service sends each webhook once, straight from the code that records the payment, every one of those hiccups loses an event, and the customer finds out weeks later when their books don&amp;rsquo;t add up.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
