Atomicity: Microservices tend to be more distributed, making atomic transactions?

Short answer: difficult. It's not easy to ensure that all services in a distributed environment either commit or roll back changes in a single, atomic transaction. Solutions like the Saga pattern or Eventual Consistency are commonly used instead.

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

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.