What is the Saga pattern, and when would you use it in microservices?

Short answer: The Saga pattern is a design pattern for managing long-running distributed transactions in microservices, especially in the context of eventual consistency.

Explain a bit more

It breaks a large transaction into a series of smaller, isolated transactions that are coordinated through a sequence of events. Choreography: Each service involved in the saga listens for events and takes action accordingly (decoupled). Orchestration: A central orchestrator (e.g., a Saga Orchestrator) directs the saga, ensuring each step is performed and compensation is handled if something fails. When to use it: Long-running workflows that span multiple microservices. When you need to ensure that if a service fails, the changes made by previous services are rolled back.

Example code

In an Order Management System, if an order involves creating an order, processing payment, and updating inventory, the Saga pattern ensures each step completes successfully. If any step fails, compensation transactions (like refunding payment) are triggered.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.