<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pattern on Vubon Notes</title><link>https://vubon.me/tags/pattern/</link><description>Recent content in Pattern on Vubon Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 24 May 2026 11:00:00 +0000</lastBuildDate><atom:link href="https://vubon.me/tags/pattern/index.xml" rel="self" type="application/rss+xml"/><item><title>No-Op Update Pattern: State-Driven Idempotent Updates</title><link>https://vubon.me/posts/no-op-update-pattern/</link><pubDate>Sun, 24 May 2026 11:00:00 +0000</pubDate><guid>https://vubon.me/posts/no-op-update-pattern/</guid><description>&lt;p>After exploring &lt;a href="https://vubon.me/posts/system-design-interview-idempotency/">idempotency keys&lt;/a>, I came across another pattern that deserves more attention: the &lt;strong>No-Op Update Pattern&lt;/strong>.&lt;/p>
&lt;p>The idea is simple, but the mindset behind it is what makes it powerful.&lt;/p>
&lt;p>Instead of treating every update request as something that must trigger work, you first ask a more important question:&lt;/p>
&lt;p>&lt;strong>Does this request actually change the state?&lt;/strong>&lt;/p>
&lt;p>If the answer is no, the system should do nothing and return the current state.&lt;/p></description></item></channel></rss>