What is the role of the Saga pattern in microservices transactions?

The Saga pattern is used to manage long-running transactions in microservices without

requiring a distributed transaction (e.g., two-phase commit). It breaks down a transaction into

Follow :

smaller, isolated steps, with each step running in its own service and completing successfully

or being compensated in case of failure.

• Steps: Each microservice in a saga performs a local transaction and then publishes

an event or sends a message to the next service.

• Compensation: If any step in the saga fails, compensating actions (like rolling back

previous steps) are executed to maintain consistency.

There are two types of sagas: