Core Idea
The Fantasy Fiction Saga Pattern coordinates distributed transactions with asynchronous communication, atomic consistency per step, and a central orchestrator that coordinates via message queues without blocking.
The Fantasy Fiction Saga Pattern (AAO) coordinates distributed transactions with three defining properties: Asynchronous communication (orchestrator sends commands via message queues without blocking), Atomic consistency (each step executes as an ACID transaction with immediate consistency), and Orchestrated coordination (a central orchestrator manages workflow state and decides next steps). Named “Fantasy Fiction” because, like a serialized novel whose chapters arrive independently yet follow a coherent arc controlled by a single author, the orchestrator maintains narrative control without synchronously waiting for each step.
How It Works
- Non-blocking orchestration: Orchestrator publishes a command to a queue and immediately continues; it consumes reply events to advance state and publish the next command
- Atomic steps: Domain services execute ACID transactions locally before publishing a completion event back to the orchestrator
- Temporal decoupling with central control: Unlike Epic-Saga-Pattern (SAO), services don’t need simultaneous availability—queued messages buffer commands during transient outages
- Compensating transactions on failure: Orchestrator asynchronously publishes compensation commands in reverse order (LIFO)
Trade-Offs
Advantages:
- Higher throughput than Epic Saga—orchestrator coordinates many concurrent sagas without blocking
- Temporal decoupling—queued messages survive temporary service unavailability
- Strong consistency per step despite asynchronous transport
- Centralized error handling, compensation sequencing, and audit trail
Disadvantages:
- Requires message broker, correlation IDs, reply channels, and idempotent message handling
- Harder to trace than synchronous patterns—must correlate messages across queues
- Orchestrator remains a single point of failure; state recovery needed after crash
- Out-of-order message delivery requires sequence tracking or deduplication logic
Related Concepts
- Orchestration—Central coordinator pattern that Fantasy Fiction builds upon
- Asynchronous-Communication—Non-blocking message-based communication model
- Atomicity—ACID property that Fantasy Fiction guarantees at each step
- ACID—Transaction properties maintained within each domain service
- Distributed-Transactions—Broader category that sagas address without 2PC
- Saga-Pattern—Foundational pattern; Fantasy Fiction is one specific implementation
- Epic-Saga-Pattern - Synchronous-Atomic-Orchestrated alternative
- Software Architecture - The Hard Parts - Ford, Richards, Sadalage & Dehghani - 2022—Primary source defining eight saga variations
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”, pages 325-345
-
Richardson, Chris (2025). “Pattern: Saga.” Microservices.io.
-
Garcia-Molina, Hector and Salem, Kenneth (1987). “Sagas.” ACM SIGMOD Record, Vol. 16, No. 3, pp. 249-259. DOI: 10.1145/38714.38742
-
Hohpe, Gregor and Woolf, Bobby (2003). Enterprise Integration Patterns. Addison-Wesley. ISBN: 978-0321200686.
-
Amazon Web Services (2025). “Standard vs Express Workflows.” AWS Step Functions.
Note
This content was drafted with assistance from AI tools for research, organization, and initial content generation. All final content has been reviewed, fact-checked, and edited by the author to ensure accuracy and alignment with the author’s intentions and perspective.