other

Inbox pattern

A messaging design pattern in which a consumer stores each received event's identifier and processing state in its own database, so repeated deliveries of the same event can be detected and skipped.

Known aliases

idempotent consumer pattern

Relationships

No evidence-backed relationships are recorded.

Current clusters

build1 publisher

Marking the Inbox row PROCESSED before the business commit suppresses the retry

The Inbox pattern makes a consumer idempotent only when the dedup row and the business write commit together, and a Spring Boot walkthrough works through what each of the two wrong orderings costs you.

Publishers:dev.to

Reality

Evidence58
Adoption: Insufficient
Hype gap−10
Incentives25
Confidence62