SAGA a failure-management and data-consistency pattern used in distributed microservices architecture. Definition: A sequence of local transactions that update data across multiple independent services Eventual Consistency: Instead of locking resources globally across a network like traditional ACID transactions, each step commits locally and triggers the next step via events or messages . Compensating Transactions: If a step fails halfway through the sequence, the saga runs a series of undo operations (compensations) to roll back the changes made by the preceding Core Coordination Methods Choreography: Decentralized approach where each microservice publishes domain events that passively trigger the next service Orchestration: Centralized approach where a dedicated coordinator object tells each participant exactly which local transactions to run and when. [ 1 , 2 ]