<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Youssef Ben Henda on foojay.io - Friends Of OpenJDK</title><link>http://foojayio.github.io/website/today/author/youssef/</link><description>Articles written by Youssef Ben Henda on foojay.io - Friends Of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 04 Aug 2026 22:11:22 +0000</lastBuildDate><atom:link href="http://foojayio.github.io/website/today/author/youssef/index.xml" rel="self" type="application/rss+xml"/><item><title>Idempotent Spring Boot: Safe REST with One Annotation</title><link>http://foojayio.github.io/website/today/idempotent-spring-boot-starter/</link><pubDate>Tue, 04 Aug 2026 22:11:22 +0000</pubDate><guid>http://foojayio.github.io/website/today/idempotent-spring-boot-starter/</guid><description>&lt;h2 id="idempotent-rest-endpoints-without-the-boilerplate"&gt;Idempotent REST Endpoints Without the Boilerplate&lt;/h2&gt;&#10;&lt;h2 id="stop-charging-your-users-twice-idempotent-rest-endpoints-with-one-annotation"&gt;Stop Charging Your Users Twice: Idempotent REST Endpoints with One Annotation&lt;/h2&gt;&#10;&lt;h2 id="the-problem-nobody-talks-about-until-production"&gt;The problem nobody talks about until production&lt;/h2&gt;&#10;&lt;p&gt;A user taps &amp;ldquo;Pay.&amp;rdquo; The request times out. Their app retries. Your server charges them twice.&lt;/p&gt;&#10;&lt;p&gt;You didn&amp;rsquo;t write a bug. The network did. But your users don&amp;rsquo;t care about that distinction.&lt;/p&gt;&#10;&lt;p&gt;The idempotency problem shows up in more places than payments. A load balancer replays a timed-out request. A mobile client double-taps a submit button. A Kubernetes pod retries after a restart. From the server&amp;rsquo;s perspective, all of these look identical: a second POST that arrives after the first one already executed.&lt;/p&gt;</description></item></channel></rss>