<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Releases on Inorderly.com</title>
    <link>https://inorderly.com/tags/releases/</link>
    <description>Recent content in Releases on Inorderly.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://inorderly.com/tags/releases/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Inorderly 0.1 Turns Late, Duplicate and Out of Order Events Into One Repeatable Sequence</title>
      <link>https://inorderly.com/inorderly-0.1-turns-late-duplicate-and-out-of-order-events-into-one-repeatable-sequence/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://inorderly.com/inorderly-0.1-turns-late-duplicate-and-out-of-order-events-into-one-repeatable-sequence/</guid>
      <description>&lt;p&gt;Events don&amp;rsquo;t arrive the way they happened. A webhook gets retried and the same order turns up twice. A payment service&amp;rsquo;s clock runs behind the checkout&amp;rsquo;s, so the payment looks older than the order it pays for. A price feed delivers tick 88 before tick 87. Every pipeline that takes events from more than one place has some code to deal with this, and that code usually gives a slightly different answer each time it runs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
