<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Distributed Systems on API Course</title>
    <link>https://apicourse.com/tags/distributed-systems/</link>
    <description>Recent content in Distributed Systems on API Course</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicourse.com/tags/distributed-systems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Idempotency in APIs: Building Operations That Are Safe to Retry</title>
      <link>https://apicourse.com/idempotency-in-apis-building-operations-that-are-safe-to-retry/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>https://apicourse.com/idempotency-in-apis-building-operations-that-are-safe-to-retry/</guid>
      <description>&lt;p&gt;Networks fail. Connections drop. Load balancers time out. Servers restart mid-request. In a distributed system, any request that travels over a network can be sent but not confirmed, leaving the caller uncertain whether the operation completed. This is not a rare edge case — it is a routine condition that well-designed APIs must handle. Idempotency is the mechanism that makes retrying safe when certainty is unavailable.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-idempotency-means&#34;&gt;What Idempotency Means&lt;/h2&gt;&#xA;&lt;p&gt;An operation is idempotent if performing it multiple times produces the same result as performing it once. The outcome is identical whether you call it one time or ten times; subsequent calls do not change anything that the first call already changed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
