# Overview of Causality #flashcard A level of [[Consistency]] where the data is not treated as a single copy, but the ordering of events is preserved. Some things can be concurrent, so the version history is like a timeline with branching and merging. <!--ID: 1751507776948--> # Key Considerations - One method for implement causal consistency is using [[Lamport Timestamps]] # Pros of Causality #flashcard - Causal consistency does not have the coordination overhead of linearizability and is much less sensitive to network problems <!--ID: 1751507776950--> # Cons # Use Cases # Related Topics