In this situation—booking travel, charging, then failing to reserve lodging—which choice best applies “Sagas Coordinate Compensating Actions”?

A saga sequences distributed transactions and defines compensations when later steps fail. Compensation is a new domain action and may not perfectly erase the original effect.

Event sourcing stores an append-only sequence of domain events and derives current state by replay. It improves auditability but requires event versioning, snapshots, and privacy-aware correction strategies.

Event Sourcing Rebuilds State From Accepted Events

Queues may redeliver and workers may crash between effects and acknowledgements. Exactly-once business behavior usually comes from deduplication, transactions, and idempotent consumers, not transport promises alone.

Exactly-Once Effects Are an End-to-End Claim

IETF Trust and the named RFC authors

Canonical URL: https://www.rfc-editor.org/rfc/rfc9110.html
License: IETF Trust Legal Provisions
Restrictions: Link and summarize independently. The RFC carries IETF Trust terms and a pre-5378 restriction; do not create a derivative outside permitted standards-process uses.

HTTP Semantics (RFC 9110) — Graph Engineering Course Source

Consensus protocols let non-faulty replicas agree on an ordered log despite some failures. They solve replicated state agreement, not truth, fairness, or model hallucination.

Distributed Consensus Orders Shared Decisions

In this situation—reconstructing how a course plan changed after learner feedback—which choice best applies “Event Sourcing Rebuilds State From Accepted Events”?

Sagas Coordinate Compensating Actions

In this situation—ensuring one approved notification is sent despite message redelivery—which choice best applies “Exactly-Once Effects Are an End-to-End Claim”?

Learn Before

Related

Learn After