Backend reliability 路 interactive lab

Async Task Reliability Lab

See why retries can duplicate work鈥攁nd how idempotency keys and a transactional outbox change the failure story.

Configure a failure

3

One synthetic request 路 deterministic outcomes 路 no real services

Completed once

Attempts: 2 路 Effects committed: 1

Strategy: Naive retryScenario: Commit lost

What happened

Event timeline

TimeEventDetail

Idempotency / outbox ledger

Naive retries

Repeat a side effect after an ambiguous response, risking duplicate work.

Idempotency key

Store a result by request key so a retry can replay the first outcome.

Transactional outbox

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.