liveBook · Manning

Consistency

As explained in Acing the Frontend Interview

Consistency is the property that reads observe data according to a specified agreement about the ordering and visibility of writes.

Consistency specifies what data reads may observe after writes, making it a central trade-off in distributed systems and a common interview topic. Under CAP, consistency means every read receives the latest write or an error; partition tolerance forces a choice between consistency and availability during network failures. section 6.2

Use these distinctions when analyzing a distributed architecture:

  • Strong consistency provides the latest value or an error, while eventual consistency allows replicas to converge over time. section 6.2
  • CP systems such as HBase prioritize consistency during partitions; AP systems such as DynamoDB prioritize availability and typically provide eventual consistency. section 6.2

Interview scenario

When a network partition separates replicas, ask whether the system should reject or delay reads and writes to preserve consistency, or continue serving potentially stale data to preserve availability. Justify the choice against the application’s requirements. section 6.2

How Acing the Frontend Interview covers it

How deep it goes
Explains CAP semantics, compares consistency models, classifies systems, and reaches architectural evaluation without detailing implementation internals.
Examples
Uses HBase, DynamoDB, PostgreSQL financial applications, Cassandra, and social-media feeds to illustrate consistency choices.
What it assumes
Assumes distributed-system fundamentals while defining CAP properties and basic consistency models from first principles.
What you can do after
Evaluate consistency and availability choices during partitions and select models appropriate to system requirements.
How it connects
Connects consistency with CAP theorem, availability, partition tolerance, strong consistency, eventual consistency, causal consistency, and read-your-writes consistency.

Also explained in

Compare how 28 books explain consistency →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Acing the Frontend Interview. The section links point to the parts of the book it draws on.