Acknowledgement
A response that confirms a contract-defined milestone, such as durable receipt. It does not necessarily mean the business effect has completed.Read in context ↗
At-least-once delivery
A delivery model that permits repeated delivery while pursuing receipt. A finite retry budget can still exhaust; eventual success depends on additional assumptions.Read in context ↗
At-most-once delivery
A model that avoids repeating a delivery but may lose work. The lab’s once mode makes one attempt and provides no recovery.Read in context ↗
Backoff
A delay before another attempt. Increasing delays reduce immediate retry pressure; they do not make an unsafe operation safe to repeat.Read in context ↗
Business effect
The intended state change, such as completing a session. Count it separately from requests, log records and acknowledgements.Read in context ↗
Callback
An asynchronous notification delivered to a receiver. In this manual it is an event envelope, not a promise of a particular vendor protocol.Read in context ↗
Canonical identity
The stable identity used to recognize one logical record or operation across different representations, translations and deliveries.Read in context ↗
Correlation ID
An identifier used to connect related records. Its scope must be explicit: a request, a longer operation and a delivery are different things.Read in context ↗
Cursor
An opaque continuation value for walking a collection. Clients should use the documented token rather than derive their own page position.Read in context ↗
Dead letter
An event retained after the configured processing or delivery budget is exhausted. The label alone does not prove that no effect occurred.Read in context ↗
Deduplication
Recognizing a repeated logical event and suppressing an unwanted repeated effect within a defined scope and retention window.Read in context ↗
Delivery attempt
One attempt to pass an envelope across a boundary. Several attempts may concern the same logical event.Read in context ↗
Event envelope
Metadata and payload carried together, commonly including an event identity and schema version. Our example field names are invented.Read in context ↗
Exactly-once claim
A guarantee that only becomes meaningful when its effect boundary, failure assumptions and lifetime are named. It is not implied by a queue label.Read in context ↗
Idempotency
The property that repeating an operation has the same intended effect as performing it once. Responses and diagnostic records may still differ.Read in context ↗
Idempotency key
A caller-supplied or protocol-defined identity for a logical operation. The receiver must enforce its scope and handle changed intent.Read in context ↗
Inbox
A durable receiver-side record of accepted events, allowing asynchronous processing after the delivery endpoint acknowledges receipt.Read in context ↗
Jitter
Variation added to retry timing to reduce synchronized retries. The lab omits randomness so its virtual trace is deterministic.Read in context ↗
Lease
A time-bounded claim to perform work. An expired lease does not prove that the old worker stopped, so effects still need protection.Read in context ↗
Outbox
A durable record of work to dispatch, written alongside local state in the same transaction in the design shown here. Dispatch may repeat.Read in context ↗
Pagination
Retrieving a collection in bounded portions. A short page does not necessarily mean the collection has ended.Read in context ↗
Reconciliation
Comparing durable facts across boundaries to resolve an uncertain outcome. It needs a stable reference and an actual lookup or repair process.Read in context ↗
Redaction
Removing or replacing sensitive information before it reaches an inappropriate destination. Preventing collection is often a stronger first boundary.Read in context ↗
Replay
Deliberately delivering an existing event again. Preserving its business identity helps distinguish recovery from a new operation.Read in context ↗
Retry budget
A bound on extra attempts, elapsed time or both. The lab counts retries as attempts after the initial one.Read in context ↗
Schema version
An explicit marker for the structure and interpretation of an event. Valid JSON alone does not establish schema compatibility.Read in context ↗
Snapshot
A coherent version of a collection under a stated consistency model. Multiple pages do not automatically belong to the same snapshot.Read in context ↗
Timeout
A deadline after which a caller stops waiting. It describes the caller’s observation, not proof that a remote effect was rolled back.Read in context ↗
Tombstone
An explicit deletion marker in a change feed. It avoids inferring deletion merely because a record was not seen during an incomplete import.Read in context ↗
Trace context
Metadata linking spans of a distributed operation. W3C defines propagation headers; these are not credentials or authorization evidence.Read in context ↗