<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Yuelin Ou on foojay.io - Friends Of OpenJDK</title><link>http://foojayio.github.io/website/today/author/yuelin-ou/</link><description>Articles written by Yuelin Ou on foojay.io - Friends Of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 17 Aug 2026 06:46:00 +0000</lastBuildDate><atom:link href="http://foojayio.github.io/website/today/author/yuelin-ou/index.xml" rel="self" type="application/rss+xml"/><item><title>Idempotent Write Paths: Keeping an Integration Pipeline Correct When Messages Repeat</title><link>http://foojayio.github.io/website/today/idempotent-write-paths-keeping-an-integration-pipeline-correct-when-messages-repeat/</link><pubDate>Mon, 17 Aug 2026 06:46:00 +0000</pubDate><guid>http://foojayio.github.io/website/today/idempotent-write-paths-keeping-an-integration-pipeline-correct-when-messages-repeat/</guid><description>&lt;h2 id="a-reconciliation-that-didnt-add-up"&gt;A reconciliation that didn&amp;rsquo;t add up&lt;/h2&gt;&#10;&lt;p&gt;Let me start with a real one. After a big sales promo, during reconciliation, finance said a batch of orders had the wrong status: on our side it showed &amp;ldquo;paid&amp;rdquo;, but the finance system hadn&amp;rsquo;t booked it.&lt;/p&gt;&#10;&lt;p&gt;Tracing it back, we found the payment gateway had retried during its peak, and the same payment notification got pushed twice. The first one was processed normally; the second time it came, the consumer happened to be in the middle of a rolling restart, so the message got re-queued and consumed again.&lt;/p&gt;</description></item></channel></rss>