Which scenario is appropriate for eventual consistency?

Which scenario is appropriate for eventual consistency?

• A. Like counts on a social feed may be slightly out of date briefly.
• B. Bank account balance must be exact immediately.
• C. Transaction postings must be strong-consistent for compliance.
• D. Real-time inventory for checkout.

Answer: (A)

Eventual consistency is about allowing updates to propagate asynchronously so that all replicas converge to the same state over time, even if some reads see slightly stale data in the short term. This approach works well when exact, immediate accuracy isn’t critical and high availability is preferred. The like counts scenario fits this pattern: a like event may be processed on one server before others catch up, so the displayed count might be a little off for a moment. Because the exact value isn’t crucial to the user experience and the system can tolerate tiny discrepancies, eventual consistency is appropriate here. In contrast, bank account balances must be exact immediately to prevent financial errors and inconsistencies, requiring strong consistency. Transaction postings for compliance similarly need a precise, auditable order of events, which strong or linearizable consistency provides. Real-time inventory for checkout also needs up-to-date stock levels to avoid overselling, which again points to strong or tightly controlled consistency. So the scenario that aligns with eventual consistency is the like counts on a social feed, where brief staleness is acceptable and convergence is acceptable over time.

Eventual consistency is about allowing updates to propagate asynchronously so that all replicas converge to the same state over time, even if some reads see slightly stale data in the short term. This approach works well when exact, immediate accuracy isn’t critical and high availability is preferred.

The like counts scenario fits this pattern: a like event may be processed on one server before others catch up, so the displayed count might be a little off for a moment. Because the exact value isn’t crucial to the user experience and the system can tolerate tiny discrepancies, eventual consistency is appropriate here.

In contrast, bank account balances must be exact immediately to prevent financial errors and inconsistencies, requiring strong consistency. Transaction postings for compliance similarly need a precise, auditable order of events, which strong or linearizable consistency provides. Real-time inventory for checkout also needs up-to-date stock levels to avoid overselling, which again points to strong or tightly controlled consistency.

So the scenario that aligns with eventual consistency is the like counts on a social feed, where brief staleness is acceptable and convergence is acceptable over time.