💾Durability

NEW

Also known as: Transaction Durability, Persistent Commit

The guarantee that once a transaction commits, its data persists and survives system failures.

DESCRIPTION

Durability is the ‘D’ in ACID, ensuring committed changes are permanently recorded. Systems implement durability using write-ahead logs, journaling, synchronous replication, and reliable storage. It underpins recovery strategies, enabling databases to restore committed state after crashes. Durability can trade off with latency and throughput when using synchronous writes. Cloud services often expose durability SLAs through multi-zone replication.

ALTERNATIVE DEFINITIONS

Wikipedia

Durability (D) means that once a transaction has been committed, it will remain so, even in the event of power loss, crashes, or errors.

Explicitly ties durability to surviving failures after commit.

Source

Microsoft Learn

Durability means that the effects of a completed transaction are permanently recorded and survive system failures.

Highlights permanence and survival of failures in SQL Server context.

Source

Oracle

Durability ensures that the results of a committed transaction are permanent, even in the event of system failure.

Emphasizes permanence across failures in Oracle databases.

Source

RELATED TERMS

ACID Atomicity Consistency Isolation Write-Ahead Logging Replication Crash Recovery Journaling InnoDB Transaction Log

COMPETING TERMS

BASE

KNOWLEDGE AREAS

Data Storage & Operations Data Engineering Data Architecture Data Management Data Security

TARGET AUDIENCE

Data Engineer Data Architect Cloud Architect DevOps Engineer Software Developer Application Administrator IT Manager Security Architect

EXTERNAL SOURCES

• Wikipedia - ACID
• PostgreSQL - Write-Ahead Logging overview
• MySQL - InnoDB redo logging durability
• Google Cloud - Synchronous replication durability
• AWS - Well-Architected resilience guidance

TOP QUESTIONS

Why is Durability crucial for transaction processing?

It guarantees committed data remains intact after failures, enabling reliable recovery. Without durability, systems risk data loss and inconsistent states.

Category: Relevancy

How is Durability implemented in databases?

Via write-ahead logs, fsync, journaling, checkpoints, and replication. These mechanisms ensure committed state can be reconstructed post-crash.

Category: Management

What trade-offs affect Durability performance?

Synchronous writes increase latency; batching and group commit optimize throughput. Strong durability can reduce peak performance.

Category: Performance

How does Durability relate to BASE systems?

BASE favors availability and eventual consistency, sometimes deferring durable writes. ACID emphasizes immediate durable commits.

Category: Alternatives

What is a common mistake regarding Durability?

Disabling fsync or relying on cache without proper flushes can risk data loss during crashes. Always validate storage guarantees.

Category: Mistakes

How do cloud platforms provide Durability?

Through multi-zone replication, managed logging, and SLA-backed durability guarantees. Verify configuration for synchronous behavior.

Category: Overview

What is the risk of misconfiguring Durability?

Data loss, corrupted state, and prolonged recovery times. Compliance violations may arise for regulated workloads.

Category: Risk

Is Durability always required at the strongest level?

Not necessarily; some workloads accept relaxed durability for latency gains. Choose levels based on business impact.

Category: Opinion

How to test Durability in practice?

Simulate crashes and power failures, verify recovery, and audit logs. Use chaos engineering for robust validation.

Category: Testing