Event-Driven Architecture: Each service maintains eventual consistency by producing events to notify other services of changes, and other services react to these events to update their state. Example: If the Order Service and Inventory Service both need to update their databases
Answer: s part of a transaction, you might use a saga to ensure that, if an error occurs, the system rolls back any changes made in the previous services.
What interviewers expect
- A clear definition tied to Microservices in Microservices projects
- Trade-offs (performance, maintainability, security, cost)
- When you would and would not use it in production
Real-world example
In a production Microservices application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.
How to explain in the interview
- Define the concept in one or two sentences.
- Context — where it fits in Microservices architecture.
- Example — a specific project, bug, or performance win.
- Trade-off — what you gain vs what you sacrifice.
Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.