eventual consistency concept
If writes stop, all replicas eventually converge to the same state.
If writes stop, all replicas eventually converge to the same state. The 'eventual' part is silent on bound — could be milliseconds, could be hours during a partition. Stronger sub-models layer on guarantees: read-your-writes, monotonic reads, causal consistency, session consistency. Eventual consistency is what AP systems sacrifice consistency for, and the source of most 'I just wrote it, why isn't it there?' bugs in the field. The fix is usually a stronger consistency tier for the specific read path that needs it (e.g. read from primary), not making the whole system strongly consistent.
After writes stop, all replicas will eventually agree. Read-your-writes, monotonic reads, and causal consistency are stronger sub-flavors.