📝 Blogged: "On Idempotency Keys"
Discussing several options for ensuring exactly-once processing in distributed systems using idempotency keys, from UUIDs to monotonically increasing sequences.
👉 www.morling.dev/blog/on-idem...
Discussing several options for ensuring exactly-once processing in distributed systems using idempotency keys, from UUIDs to monotonically increasing sequences.
👉 www.morling.dev/blog/on-idem...
November 25, 2025 at 4:38 PM
📝 Blogged: "On Idempotency Keys"
Discussing several options for ensuring exactly-once processing in distributed systems using idempotency keys, from UUIDs to monotonically increasing sequences.
👉 www.morling.dev/blog/on-idem...
Discussing several options for ensuring exactly-once processing in distributed systems using idempotency keys, from UUIDs to monotonically increasing sequences.
👉 www.morling.dev/blog/on-idem...
Ah, yes. The idempotency of lasagna.
If you put a lasagna on top of another lasagna, it’s no longer two lasagnas. It’s one giant lasagna. THAT is the power of lasagna.
September 26, 2026 at 1:34 PM
Ah, yes. The idempotency of lasagna.
Building event-driven systems? Need help understanding idempotency? I created a visual to help 👇
eda-visuals.boyney.io/visuals/unde...
eda-visuals.boyney.io/visuals/unde...
Understanding Idempotency
What does it mean to have idempotent consumers? Why is it important?
eda-visuals.boyney.io
December 9, 2024 at 8:04 PM
Building event-driven systems? Need help understanding idempotency? I created a visual to help 👇
eda-visuals.boyney.io/visuals/unde...
eda-visuals.boyney.io/visuals/unde...
Idempotency is a powerful concept: many developers need it, but it is hard to get right. It means you can run an operation multiple times and get the same outcome as running it once. Combine idempotency with retries, and you achieve effectively exactly once execution.
January 7, 2025 at 5:00 PM
Idempotency is a powerful concept: many developers need it, but it is hard to get right. It means you can run an operation multiple times and get the same outcome as running it once. Combine idempotency with retries, and you achieve effectively exactly once execution.
Don't repeat yourself
Async
Verbosity
Idempotency
Don't repeat yourself
Async
Verbosity
Idempotency
Don't repeat yourself
March 11, 2024 at 6:47 PM
Don't repeat yourself
Async
Verbosity
Idempotency
Don't repeat yourself
Async
Verbosity
Idempotency
Don't repeat yourself
Laravel Payment Reconciliation - Reliable Payment State & Webhook Idempotency
Laravel Payment Reconciliation - Reliable Payment State & Webhook Idempotency
Reliable payment reconciliation for Laravel — detect and resolve mismatches between payment providers and your application. - raedcodes/laravel-payment-reconciliation
laravel-news.com
September 24, 2026 at 5:01 PM
Laravel Payment Reconciliation - Reliable Payment State & Webhook Idempotency
A practical guide to idempotency keys, IETF standards, and safe retries with Quarkus
www.the-main-thread.com/p/java-idemp...
www.the-main-thread.com/p/java-idemp...
February 4, 2026 at 8:15 AM
A practical guide to idempotency keys, IETF standards, and safe retries with Quarkus
www.the-main-thread.com/p/java-idemp...
www.the-main-thread.com/p/java-idemp...
"A handler that's safe to retry sequentially is a handler that has never been tested. Run two copies at once and see what your database says."
Your Idempotency Check Has a Race in It
Why check-then-act idempotency fails under concurrency, and how to fix it with unique constraints, atomic upserts, and optimistic concurrency.
irina.codes
September 25, 2026 at 11:01 PM
"A handler that's safe to retry sequentially is a handler that has never been tested. Run two copies at once and see what your database says."
Stage 2 runs Safety Gate assertions to block bad payloads. Stage 3 writes every request to an Execution Record to guarantee idempotency across network retries.
September 26, 2026 at 11:05 PM
Stage 2 runs Safety Gate assertions to block bad payloads. Stage 3 writes every request to an Execution Record to guarantee idempotency across network retries.
Your AI Agent Needs an Unknown State
A timeout does not prove an AI agent’s action failed. Here’s how explicit unknown states, idempotency, and reconciliation can prevent duplicate effects.
#hackernews #news
A timeout does not prove an AI agent’s action failed. Here’s how explicit unknown states, idempotency, and reconciliation can prevent duplicate effects.
#hackernews #news
Your AI Agent Needs an Unknown State
A timeout does not prove an AI agent’s action failed. Here’s how explicit unknown states, idempotency, and reconciliation can prevent duplicate effects.
hackernoon.com
September 26, 2026 at 12:01 PM
Your AI Agent Needs an Unknown State
A timeout does not prove an AI agent’s action failed. Here’s how explicit unknown states, idempotency, and reconciliation can prevent duplicate effects.
#hackernews #news
A timeout does not prove an AI agent’s action failed. Here’s how explicit unknown states, idempotency, and reconciliation can prevent duplicate effects.
#hackernews #news
ICYMI: Why Retries Break Your Java APIs (And How Idempotency Fixes It) buff.ly/z1AC7Qk
Why Retries Break Your Java APIs (And How Idempotency Fixes It)
How to make retries safe, prevent duplicate writes, and implement idempotency correctly with Quarkus
www.the-main-thread.com
February 4, 2026 at 7:39 AM
ICYMI: Why Retries Break Your Java APIs (And How Idempotency Fixes It) buff.ly/z1AC7Qk
Whisper, you can transcribe "squircles" correctly but not "idempotency"? wild. (although "item potency" was a good attempt)
August 1, 2025 at 7:07 PM
Whisper, you can transcribe "squircles" correctly but not "idempotency"? wild. (although "item potency" was a good attempt)
As a father of three, I'm used to things being destroyed by accident, so the ability of kubernetes to automatically deal with node failures and the idempotency of containers in general fill me with confidence.
October 22, 2025 at 12:03 PM
As a father of three, I'm used to things being destroyed by accident, so the ability of kubernetes to automatically deal with node failures and the idempotency of containers in general fill me with confidence.
Teaching Idempotency using my favourite card game while making a Silicon Valley "always blue" reference.
Having fun like this is what keeps me making videos.
Lord knows it's not the views! 🤣
Having fun like this is what keeps me making videos.
Lord knows it's not the views! 🤣
June 1, 2026 at 11:24 AM
Teaching Idempotency using my favourite card game while making a Silicon Valley "always blue" reference.
Having fun like this is what keeps me making videos.
Lord knows it's not the views! 🤣
Having fun like this is what keeps me making videos.
Lord knows it's not the views! 🤣
Codehooks: "Being able to answer questions about a webhook three weeks later is a different job, and it is the one that tends to get skipped." Kin Score 41.7, and idempotency is unlit on its own API.
https://apis.io/2026/09/22/codehooks-store-the-webhook-before-you-process-it/
https://apis.io/2026/09/22/codehooks-store-the-webhook-before-you-process-it/
September 22, 2026 at 6:42 PM
Codehooks: "Being able to answer questions about a webhook three weeks later is a different job, and it is the one that tends to get skipped." Kin Score 41.7, and idempotency is unlit on its own API.
https://apis.io/2026/09/22/codehooks-store-the-webhook-before-you-process-it/
https://apis.io/2026/09/22/codehooks-store-the-webhook-before-you-process-it/
Safely Retry API calls in Laravel laravel-news.com/idempotency-...
Safely Retry API calls in Laravel - Laravel News
Idempotency for Laravel is a production-ready package for implementing idempotency in API requests. Clients can safely retry API calls using this package without worrying about duplicate processing.
laravel-news.com
April 24, 2025 at 1:01 PM
Safely Retry API calls in Laravel laravel-news.com/idempotency-...
Tiny word, important idea: Idempotency. It is one of the best tools for surviving retries safely.
#buildinpublic #indiedev
#buildinpublic #indiedev
July 22, 2026 at 1:16 PM
Tiny word, important idea: Idempotency. It is one of the best tools for surviving retries safely.
#buildinpublic #indiedev
#buildinpublic #indiedev
was not expecting the least reliable part of reg this year to be hitting square's API, we got around 100 timeout errors over the weekend x.x
might try updating things to aggressively retry with much shorter timeouts because the idempotency key should prevent anything from duplicating...
might try updating things to aggressively retry with much shorter timeouts because the idempotency key should prevent anything from duplicating...
March 10, 2025 at 4:25 PM
was not expecting the least reliable part of reg this year to be hitting square's API, we got around 100 timeout errors over the weekend x.x
might try updating things to aggressively retry with much shorter timeouts because the idempotency key should prevent anything from duplicating...
might try updating things to aggressively retry with much shorter timeouts because the idempotency key should prevent anything from duplicating...
A timeout does not prove an AI agent’s action failed. Here’s how explicit unknown states, idempotency, and reconciliation can prevent duplicate effects. #aiagents
Your AI Agent Needs an Unknown State
hackernoon.com
September 25, 2026 at 11:25 AM
A timeout does not prove an AI agent’s action failed. Here’s how explicit unknown states, idempotency, and reconciliation can prevent duplicate effects. #aiagents
Recently, I attended various sessions at QCon London 2025, and one that I liked in particular was Sam Newman´s session on Timeouts, Retries, and Idempotency in Distributed Systems… #qcon #integration #resiliency #distributedcomputing sjwiggers.com/2025/04/18/r...
Resilient by Design — Timeouts, Retries, and Idempotency
Recently, I attended various sessions at QCon London 2025, and one that I liked in particular was Sam Newman´s session on Timeouts, Retries, and Idempotency in Distributed Systems. My InfoQ colleag…
sjwiggers.com
April 19, 2025 at 8:27 AM
Recently, I attended various sessions at QCon London 2025, and one that I liked in particular was Sam Newman´s session on Timeouts, Retries, and Idempotency in Distributed Systems… #qcon #integration #resiliency #distributedcomputing sjwiggers.com/2025/04/18/r...
You can automate the provisioning of infrastructure using tools like Cobbler, Terraform, or shell scripts depending on the API you're working with. You are essentially encoding configuration decisions into a tool and running it. Hopefully the target API supports idempotency.
October 21, 2024 at 2:08 PM
You can automate the provisioning of infrastructure using tools like Cobbler, Terraform, or shell scripts depending on the API you're working with. You are essentially encoding configuration decisions into a tool and running it. Hopefully the target API supports idempotency.
this is not some kind of a hack. it's one of the most exciting consequences of the functional programming paradigm. purity or idempotency make it safe to move stuff around without changing the final outcome. following the "rules of react" is just ensuring your code is safe to move around like this
October 9, 2025 at 7:13 PM
this is not some kind of a hack. it's one of the most exciting consequences of the functional programming paradigm. purity or idempotency make it safe to move stuff around without changing the final outcome. following the "rules of react" is just ensuring your code is safe to move around like this
Yes 100%.
We can never use llms alone for any sort of safety check, or for any use case where correctness is required.
And considering that’s primarily how we use computers, it’s a huge paradigm shift! Idempotency has been baked into user expectations whether they know it or not.
We can never use llms alone for any sort of safety check, or for any use case where correctness is required.
And considering that’s primarily how we use computers, it’s a huge paradigm shift! Idempotency has been baked into user expectations whether they know it or not.
March 31, 2026 at 8:22 PM
Yes 100%.
We can never use llms alone for any sort of safety check, or for any use case where correctness is required.
And considering that’s primarily how we use computers, it’s a huge paradigm shift! Idempotency has been baked into user expectations whether they know it or not.
We can never use llms alone for any sort of safety check, or for any use case where correctness is required.
And considering that’s primarily how we use computers, it’s a huge paradigm shift! Idempotency has been baked into user expectations whether they know it or not.