Menu

A repeated confirmation is not an exactly-once guarantee
📰

A repeated confirmation is not an exactly-once guarantee

DEV Community: webdev·allowfy·1 day ago
#fzP4eAxD
#devtowebdev#devto#dev#terminal#exactly
Reading 0:00
15s threshold

Seeing the same successful response twice can be reassuring, but it is not the same as proving exactly-once execution. A terminal response may be idempotent at the API surface while the underlying system still needs separate evidence for durable writes, retries, and recovery.

What the documented QA run observed

In a documented QA run of our gateway, repeating a confirmation after the operation was terminal returned the same succeeded result and the same confirmed_at value. The result was marked test:true . An earlier 12-entry fixture export also showed one operation.confirmed event and one operation.succeeded event for that fixture.

Those observations support a precise statement: the tested terminal retry presented the same result, and the available earlier event fixture contained one recorded confirmation and one recorded success.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.