How does the Event Sourcing pattern fit into microservices?

Short answer: Event Sourcing is a pattern where state changes are not stored directly in a database, but instead, each state transition (or change) is stored as an event. The state of the system can be recreated by replaying these events. In a microservices architecture, each service stores and manages its own events, which makes it easier to decouple services and manage their state independently. How it fits into 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.