<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tech on Coffee Coded</title>
    <link>https://blog.coffeecoded.dev/tech/</link>
    <description>Recent content in Tech on Coffee Coded</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 18 May 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.coffeecoded.dev/tech/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Handling Webhooks Safely: Idempotency Keys in Spring Boot</title>
      <link>https://blog.coffeecoded.dev/tech/idempotency-keys-spring-boot/</link>
      <pubDate>Sat, 18 May 2024 00:00:00 +0000</pubDate>
      <guid>https://blog.coffeecoded.dev/tech/idempotency-keys-spring-boot/</guid>
      <description>&lt;p&gt;When integrating with external systems like Stripe or PayPal, you typically rely on webhooks to be notified of events. However, distributed systems guarantee &lt;em&gt;at-least-once&lt;/em&gt; delivery, meaning your application might receive the exact same webhook event multiple times.&lt;/p&gt;&#xA;&lt;p&gt;If your webhook handler creates a payment record or provisions a resource, processing the same event twice can lead to severe bugs—like double-charging a customer.&lt;/p&gt;&#xA;&lt;p&gt;This is where &lt;strong&gt;idempotency&lt;/strong&gt; comes in. An idempotent operation is one that produces the same result regardless of how many times it is executed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
