Naive retries
Repeat a side effect after an ambiguous response, risking duplicate work.
See why retries can duplicate work鈥攁nd how idempotency keys and a transactional outbox change the failure story.
One synthetic request 路 deterministic outcomes 路 no real services
Attempts: 2 路 Effects committed: 1
| Time | Event | Detail |
|---|
Repeat a side effect after an ambiguous response, risking duplicate work.
Store a result by request key so a retry can replay the first outcome.
Commit domain state and a durable event together; delivery and consumer deduplication still need real infrastructure.
Scope: teaching simulation only. It uses in-memory synthetic records, not a database or payment service; its deterministic counts are examples, not production benchmarks. A real outbox needs transactional storage, a poller, observability, and recovery procedures.