Pattern: Idempotent Consumer

Richardson, C. (2026). Pattern: Idempotent Consumer. Microservices.io.

Type

Unclassified

Intellectual base

Unclassified

Year

2026

Link

https://microservices.io/patterns/data/transactional-outbox

Cited by

2 citations across 2 artifacts.

Each citation links to the sentence it supports in the citing article.

Mechanisms

• Deduplication Table or Ledger
  • Its strength is that it is the one durable place duplicates can be recognized across channels, restarts, and time — a shared record is what lets an idempotent receiver work even when the operation itself keeps no memory.
• Transactional Outbox/Inbox Pattern
  • Its strength is eliminating the dual-write inconsistency with only a local transaction — no two-phase commit, no distributed lock — which makes it the workhorse for reliable event publishing in microservices.

    This sourceMicroservices.io (n.d.). The transactional outbox stores an outgoing message in the same local database transaction as the business update, then relays it separately, avoiding a database/broker 2PC transaction.

Verification

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Links previously used in the corpus

Before the registry existed this work was also linked 1 other way.

• https://microservices.io/patterns/communication-style/idempotent-consumer.html ×1

Registry ID ref:85394e2b9ebd · see in the full table