Distributed Resilience · interview question
What does eventual consistency mean in a checkout workflow?
Multiple choiceHardchapter-18-curatedpremiumdistributed-resilienceeventual-consistency
Answer and explanation
Correct answer
B. Different services may briefly observe different states, but asynchronous processing and compensation should converge them
Why
Distributed systems often cannot keep every service perfectly synchronized in one instant. Instead, they move toward the correct final state through messaging, retries, and compensating actions.
Test yourself on Distributed Resilience
A free test with instant, explained results. No account needed.
More Distributed Resilience questions
- Which problem might occur if correlation IDs are not propagated consistently across all services in a distributed…
- How would you explain a common approach to implementing retries in a microservices-based Java application in an…
- What could be a consequence of setting a very high threshold for failure in a circuit breaker?
- Which of the following best describes the 'Database-per-Service' pattern in a microservices architecture?
- How would you explain a potential risk when not implementing exponential backoff during retries in microservices in an…
- How does distributed tracing assist in the performance optimization of a microservice architecture?