SysTutorials

High Availability in Distributed Storage: RDA Fundamentals

· updated April 11, 2026

Understanding the difference between reliability, durability, and availability is critical when designing or operating distributed storage systems like HDFS, Ceph, or cloud object storage. These terms are often confused, but they address distinct concerns.

Durability

Durability answers: If the system fails completely, will my data survive?

Durability is about persistence to non-volatile storage. Data is durable when it’s been written to stable storage (disk, flash, or similar) in a form that can be recovered and used after any type of failure. A durable system ensures that once you acknowledge a write to the client, that data won’t be lost even if every power supply fails simultaneously.

In practice, durability is achieved through:

If a node crashes mid-write, durability doesn’t require the system to continue operating—only that previously committed data survives.

Availability

Availability answers: When a partial failure occurs, does the system keep working?

Availability means the system continues to provide its original service despite component failures. This could be a failed disk, a dead node, or a network partition. The system should continue accepting and serving requests without manual intervention.

In distributed system contexts, availability has multiple interpretations:

System availability (traditional HA): The entire system remains operational and accessible to clients, even if individual components fail. Classic examples include heartbeat-based failover with virtual IP address takeover.

Node availability (CAP Theorem context): Individual nodes that haven’t failed continue to serve requests. This is stricter—it means you can’t arbitrarily shut down healthy nodes to preserve consistency. For example, in a system that values availability over consistency, a minority partition will continue responding to writes rather than blocking to maintain a consistent state.

These interpretations matter because a system optimized for node availability might behave differently than one optimized for system availability.

Reliability

Reliability is the most ambiguous of the three terms. Different communities define it differently:

Because there’s no consensus, avoid using “reliable” or “reliability” in technical specifications. Instead, be explicit: say “the system maintains availability during node failures” or “data survives total power loss” or “the cluster reaches consensus despite network partitions.”

Practical Examples

Scenario 1: HDFS with replication factor 3

Scenario 2: Single-node database with no replication

Scenario 3: Replicated database with quorum-based writes

In Your Architecture

When designing or evaluating storage systems:

← All posts