Event-Driven Architecture: Each service maintains eventual consistency by producing events to notify other services of changes, and other services react to these events to update their state. Example: If the Order Service and Inventory Service both need to update their databases

Short answer: s part of a transaction, you might use a saga to ensure that, if an error occurs, the system rolls back any changes made in the previous services.

Real-world example (ShopNest)

After payment succeeds, ShopNest publishes OrderPaid. Inventory and Notification services react independently—no giant distributed transaction.

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.