Tag feed

#idempotency

32 posts1 followers

Explore Hashnode

Alternatives

Trending tags this week

KRKashif Rezaarchitecture-in-practice.hashnode.dev6d ago · 7 min read

Handling Duplicate Events Safely with Idempotency

In the previous article, we looked at retries and DLQ. Retries help you recover from temporary failures. But they also create a new risk: The same event may be delivered, retried, or processed more t

0

EAElias Alrgeaieliasalrgeaidev.hashnode.devAug 29 · 4 min read

How a Timeout Can Charge Your Customer Twice (And How to Stop It in Laravel)

A customer attempts a payment. The request safely reaches your server, and the transaction is performed successfully. Then, while the response is being sent back to the client, the connection drops. T

0

KGKunal Guptakunalforked.hashnode.devAug 20 · 3 min read

Why “Just Retry the Request” Isn’t Always Safe

This is pretty simple, but I thought it was interesting enough to share. Recently I was reading about idempotency and retries, and it made me realize how something as innocent as “just retry the reque

0

JCJuan Carlos Gonzalez Cabreromalkomich.hashnode.devAug 18 · 13 min read

Inside a Kafka Order Workflow: Outbox, Retries, DLQs and Idempotency

1. The Naive Workflow: First Failure Strikes When you're building your first event-driven service with Kafka, the initial implementation feels natural and clean. You have a REST endpoint that saves

0

SMSyed Muhammad Alidevstacked.hashnode.devJul 21 · 21 min read

Stripe Payment Element in Production: Webhooks, Idempotency & Testing (2026)

If you followed our guide on integrating Stripe Payment Element with Next.js 16, you already have a working checkout flow — a Payment Intent gets created, the user pays, and everyone's happy. Except "

0

RDRONI DASsystemdesignacademy.hashnode.devJul 20 · 5 min read

Designing a payment system that never loses a cent

Most systems can tolerate being a little bit wrong. A like count that is off by one, a feed that is a few seconds stale, a search result slightly out of order. Nobody gets hurt. A payment system does

0

RDRONI DASsystemdesignacademy.hashnode.devJul 20 · 5 min read

Designing a payment system that never loses a cent

Most systems can tolerate being a little bit wrong. A like count that is off by one, a feed that is a few seconds stale, a search result slightly out of order. Nobody gets hurt. A payment system does

0

RBRakesh Bhandarkarrakesh-codex.hashnode.devJul 17 · 6 min read

Implementing Idempotency Correctly in Payment Gateways

Duplicate transactions are one of the most common failure modes in distributed payment systems. In this article, we’ll explore how idempotency works, why atomic writes matter, and how to implement a p

0

JLJeremy Longshorejeremylongshore.hashnode.devJul 13 · 13 min read

Making a Fire-and-Forget Writer Safe Under Failure

There is a hook that distills a finished Claude Code session into a few durable learnings and proposes them to a shared team brain. It runs on SessionEnd. Nobody watches it. That last sentence is the

0

SHSohag Hasannotes.sohag.proJul 2 · 9 min read

Idempotency Keys and the Immutable Audit Log: Two Patterns That Make Fintech APIs Boring (In a Good Way)

You are paying for something on your phone, you tap Pay, and the spinner just sits there. No confirmation, no error, nothing. Did it go through? Your thumb hovers over the button. Tap it again and may

0

#idempotency

Search Hashnode

#idempotency

Explore Hashnode

Trending tags this week

Handling Duplicate Events Safely with Idempotency

How a Timeout Can Charge Your Customer Twice (And How to Stop It in Laravel)

Why “Just Retry the Request” Isn’t Always Safe

Inside a Kafka Order Workflow: Outbox, Retries, DLQs and Idempotency

Stripe Payment Element in Production: Webhooks, Idempotency & Testing (2026)

Designing a payment system that never loses a cent

Designing a payment system that never loses a cent

Implementing Idempotency Correctly in Payment Gateways

Making a Fire-and-Forget Writer Safe Under Failure

Idempotency Keys and the Immutable Audit Log: Two Patterns That Make Fintech APIs Boring (In a Good Way)