Why did you choose the Saga pattern specifically?

The Saga pattern is chosen for managing distributed transactions in a microservices architecture when traditional ACID transactions are impossible or too complex.

Main reasons for choosing Saga:

• Allows breaking down a long business operation into a sequence of local transactions, each executed in a separate service.
• Ensures data consistency through compensating actions in case of errors, instead of rolling back the entire transaction.
• Improves system fault tolerance and scalability.

Example: when placing an order, the product is first reserved, then money is deducted. If the money deduction fails, Saga triggers a compensating transaction — canceling the product reservation.

Thus, Saga helps manage complex business processes in distributed systems, maintaining data integrity without locks and long transactions.