Event-Driven Communication: Use event sourcing and CQRS (Command Query?

Short answer: Responsibility Segregation) patterns to handle consistency more easily, storing state changes as events and allowing services to process them asynchronously.

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.