liveBook · Manning

Availability

As explained in Acing the Frontend Interview

High availability is the property of remaining operational and able to serve requests despite component failures.

Availability means responding successfully to requests, even when the response may not contain the latest write. In distributed systems, uptime depends partly on how the system handles network partitions and component failures. section 6.2 section 6.5

Replicated account data

A primary database asynchronously replicates account data to two replicas that serve dashboard and profile reads. If the primary fails, the replicas can keep serving reads, preserving availability; those reads may not reflect the latest write. section 6.5

The CAP trade-off makes availability a design choice: during network partitions, AP systems prioritize availability over consistency, while CP systems prioritize consistency. DynamoDB is given as an AP example and HBase as a CP example. section 6.2

Table 6.6 Data replication, sharding, and partitioning
Topic
Fundamentals
Applied skills
Advanced
Data replication
Understand that data is copied across nodes to improve availability and fault tolerance.
Use leader-follower or multi-leader replication. Tune sync vs. async replication. Handle stale reads and conflicts.
Optimize replication lag, implement quorum reads/writes, and reason about consistency in geo-replicated systems.
Sharding (horizontally partitioning)
Understand that data is split across multiple databases or nodes, usually by key.
Implement horizontal scaling using range-based or hash-based sharding. Handle rebalancing and routing logic.
Design for cross-shard transactions, hotspot detection, and dynamic resharding without downtime.
Partitioning
Know that partitioning divides data into independent subsets for manageability and parallelism.
Apply vertical vs. horizontal partitioning. Use partitioning to reduce query latency and contention.
Design partition-aware data models and query strategies. Handle skew, repartitioning, and partition pruning at scale.

Compare replication fundamentals with applied and advanced techniques for maintaining availability and handling consistency trade-offs. section 6.5

How Acing the Frontend Interview covers it

How deep it goes
Defines availability and illustrates it with replication, while linking it to CAP trade-offs and failure handling.
Examples
Uses replicated account data and contrasts DynamoDB as AP with HBase as CP.
What you can do after
Apply availability and consistency trade-offs to real-world system design scenarios.
How it connects
Connects availability to the CAP theorem, consistency, partition tolerance, data replication, and fault tolerance.

Also explained in

Compare how 25 books explain availability →

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.