← Back to Topics

Eventual Consistency

The cluster centers on discussions of eventual consistency in distributed systems and databases, frequently referencing the CAP theorem, its trade-offs with availability, and examples from systems like GitHub, Cassandra, and Spanner.

📉 Falling 0.4x Databases
3,865
Comments
20
Years Active
5
Top Authors
#6069
Topic ID

Activity Over Time

2007
3
2008
9
2009
28
2010
105
2011
127
2012
148
2013
169
2014
203
2015
269
2016
276
2017
393
2018
331
2019
196
2020
274
2021
224
2022
278
2023
280
2024
312
2025
230
2026
10

Top Contributors

zzzcpan (48) marknadal (31) aphyr (30) mjb (25) jbellis (23)

Keywords

SSOT DB CAP replicache.dev dmlConfigConsistency.html youtu.be GET datastax.com i.e API consistency eventual consistent distributed eventually database cap databases transactions transactional

Sample Comments

YouSuck2 • Sep 14, 2023 • View on HN

It's called eventual consistency...

snovv_crash • Aug 9, 2022 • View on HN

Absolutely, it's more of an 'eventually consistent' system.

anonymousDan • Dec 17, 2025 • View on HN

Some kind of casual or eventual consistency related invariants perhaps?

nl • Jul 15, 2011 • View on HN

It's called eventual consistency :)

scarface74 • May 1, 2022 • View on HN

According to their system yes. It’s a bad case of eventual consistency.

dilyevsky • Jul 25, 2024 • View on HN

Ignoring CAP theorem doesn’t just mean eventually consistent - means you will lose transactions when replicas that aren’t fully replicated get corrupted. Probably not something you want to be caught doing if you’re a bank

redact207 • Nov 9, 2019 • View on HN

this just sounds like eventual consistency which can form part of a perfectly optimal design

NelsonMinar • Feb 17, 2017 • View on HN

Eventual consistency strikes again.

pavel_lishin • May 20, 2025 • View on HN

It's called "eventual consistency".

aasasd • Aug 6, 2020 • View on HN

...Is this famed ‘eventual consistency’?