← Back to the chapter · Next detail →

Technical detail · AMQP Core: Routing and Message Lifecycle

Why settlement is not proof of exactly-once work

The source delivery comparison uses AMQP 1.0 terms: settled transfers for at-most-once, unsettled transfers with an accepted disposition and retries when acknowledgement is absent for at-least-once, and coordinated two-phase settlement for its exactly-once delivery illustration. The extra coordination has the highest overhead of the three paths.

Those transfer-level descriptions do not replace the AMQP 0-9-1 acknowledgement controls used in this chapter. Nor does an accepted or settled transfer prove that a payment happened exactly once. A handler can change application state and fail before recording its acknowledgement. A retry can then repeat the effect unless the application coordinates its completion record with that change.

Treat telemetry and sensor bursts, commands and alerts, and financial effects as different consequence classes. Use broker evidence for broker acceptance, consumer evidence for processing, and duplicate-safe application updates for effects that must not repeat. Settlement and transactions need their own scope stated before anyone interprets “exactly once.”

← Back to the chapter · Next detail →