Explain the concept of eventual consistency in microservices.

Short answer: Eventual consistency is a model in distributed systems where, instead of guaranteeing immediate consistency across all nodes, the system guarantees that, given enough time, all replicas will converge to the same state.

Explain a bit more

In microservices: Services might have their own databases, and instead of synchronizing them in real-time, they propagate updates asynchronously (via events). Eventual consistency allows for better system performance and scalability but introduces the risk of temporary data inconsistencies. Example: A Shipping Service might be updated with a new order status after the Order Service has processed the order. However, there may be a short window where the two services have inconsistent data. Eventually, the system converges to a consistent state.

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.