Eventual Consistency: Most microservices architectures lean toward eventual?

Short answer: consistency where services are allowed to be temporarily inconsistent, but will eventually converge to a consistent state through events. Event-driven architectures with tools like Kafka or RabbitMQ are commonly used to propagate changes and synchronize 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.