Cap Theorem easy
What does 'Eventual Consistency' mean?
- A A condition where the data across all nodes will never achieve a synchronized or consistent state.
- B The guarantee that if no fresh updates are made to a key, all subsequent reads will eventually return identical values.
- C A policy where the database is only required to maintain consistency during specific maintenance windows.
- D A model where write operations are strictly synchronous, while read operations are processed asynchronously.
Answer: B. The guarantee that if no fresh updates are made to a key, all subsequent reads will eventually return identical values.
Eventual Consistency is a common model for High Availability (AP) systems. It acknowledges that data might be out of sync for a short period (usually milliseconds) but guarantees that all replicas will converge on the latest version if updates cease. This allows the system to remain responsive and fast while still providing a long-term consistency guarantee.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- What is a 'Split Brain' scenario?
- The PACELC theorem extends CAP by stating: Even when there is NO partition (E), the system must choose between:
- Why is a CA (Consistent + Available) system generally considered impossible for distributed web applications?
- In CAP, 'Consistency' is equivalent to:
- In the CAP Theorem, what does the 'P' stand for?
- What causes a Network Partition?