Anthology Saga Pattern

Core Idea

The Anthology Saga Pattern is a distributed transaction pattern characterized by asynchronous communication, eventual consistency, and choreographed coordination.

The Anthology Saga Pattern (AEC) coordinates distributed transactions with three defining properties: Asynchronous communication (services exchange messages via queues or event streams), Eventual consistency (the system converges to a consistent state over time), and Choreographed coordination (no central orchestrator—each service autonomously listens for events, executes local transactions, and publishes new events). It represents the most decoupled approach to multi-service transaction management.

How It Works

• Event-driven choreography: Each service knows which events to consume and which to publish based on embedded domain logic—no orchestrator dictates the sequence
• Asynchronous messaging: Services communicate through queues or event streams, enabling non-blocking operations and temporal decoupling
• Eventual consistency: Services commit local transactions immediately; the system converges as events propagate
• Compensation through events: On failure, a service publishes a compensating event that propagates rollback through the same event-driven mechanism
• No centralized state: Tracking overall transaction progress requires correlating events across services; no single component has a complete saga view

Trade-Offs

Advantages:

• Maximum scalability—no orchestration bottleneck; services scale and process events independently
• No single point of failure; saga resilience depends only on the message broker
• Maximum service autonomy and deployment independence

Disadvantages:

• Hardest pattern to debug—reconstructing saga state requires correlating distributed event logs
• No built-in saga visibility; tracking transaction progress requires external observability tooling
• Compensation logic is distributed across services with no central sequence or coordination
• Cyclic event chains and saga timeout detection require deliberate design

Related Concepts

• Choreography - Decentralized coordination approach without central orchestrator
• Eventual-Consistency - Data consistency model accepting temporary inconsistency
• Asynchronous-Communication - Non-blocking message-based service interaction
• Saga-Pattern - General pattern for managing distributed transactions with compensations
• Distributed-Transactions - Transactions spanning multiple independent services or databases
• Parallel-Saga-Pattern - Similar pattern using orchestration instead of choreography
• Software Architecture - The Hard Parts - Ford, Richards, Sadalage & Dehghani - 2022 - Primary source defining this pattern variant

Sources

• Ford, Neal; Richards, Mark; Sadalage, Pramod; Dehghani, Zhamak (2022). Software Architecture: The Hard Parts - Modern Trade-Off Analyses for Distributed Architectures. O’Reilly Media. ISBN: 978-1-492-08689-5.

  • Chapter 12: Transactional Sagas
  • Available: https://www.oreilly.com/library/view/software-architecture-the/9781492086888/ch12.html

• Garcia-Molina, Hector and Kenneth Salem (1987). “Sagas.” ACM SIGMOD Record, Vol. 16, No. 3, pp. 249-259.

  • Available: https://www.cs.cornell.edu/andru/cs711/2002fa/reading/sagas.pdf

• Microsoft Azure Architecture Center (2026). “Saga Design Pattern.” Azure Architecture Center.

  • Available: https://learn.microsoft.com/en-us/azure/architecture/patterns/saga

• Rizos, Konstantinos et al. (2022). “Enhancing Saga Pattern for Distributed Transactions within a Microservices Architecture.” Applied Sciences, Vol. 12, No. 12, Article 6242.

  • Available: https://www.mdpi.com/2076-3417/12/12/6242

Note

This note was researched and drafted with AI. How these notes are written →