Can you explain how the Event Sourcing pattern is used in microservices?

Short answer: Event Sourcing is a pattern where the state of a system is determined by a series of events (or changes) rather than storing the current state in a database. Each event represents a change in state, and all events are stored in an immutable log. In microservices:

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.