How do microservices handle distributed transactions (Saga pattern)? माइक्रोसर्विसेज़ डिस्ट्रिब्यूटेड ट्रांज़ैक्शन्स को कैसे हैंडल करते हैं (Saga पैटर्न)?

Because each microservice owns its own database, a traditional ACID transaction spanning multiple services isn't possible — there's no single database to commit or roll back atomically. The Saga pattern solves this by breaking a business transaction into a sequence of local transactions, each executed by a different service, with each step publishing an event or message that triggers the next step.

If a step fails partway through, previously completed steps are undone using compensating transactions (e.g. if payment succeeds but shipping fails, a compensating "refund payment" transaction runs) rather than a database-level rollback. Sagas are commonly implemented as either choreography (services react to each other's events independently, no central coordinator) or orchestration (a central saga orchestrator explicitly directs each step), with orchestration being easier to reason about as complexity grows.

// Choreography: OrderCreated -> InventoryReserved -> PaymentProcessed
// If PaymentFailed, a compensating InventoryReleased event follows