Skip to main content
In this lesson, we’ll explore AWS Quantum Ledger Database (QLDB) and explain why traditional databases fall short for ledger applications. QLDB offers a fully managed, immutable ledger database with transparency and cryptographic verification to meet the rigorous demands of ledger use cases.

​
Why Traditional Databases Are Not Ideal for Ledger Use Cases

Traditional databases have several limitations when used as a ledger:
  1. Mutability: Records can be updated or deleted, making data mutable rather than tamper-proof.
  2. Lack of Transparency: Data changes can be hard to trace, impeding auditability.
  3. Centralization: Managed by a single entity, they do not support decentralized, multi-party systems.
  4. Single Point of Failure: Centralized servers can become a single point of vulnerability.
  5. Absence of Consensus Mechanisms: They lack built-in methods for distributed trust.
  6. Limited Privacy Features: Advanced privacy options like selective disclosure or confidential transactions are often missing.
QLDB addresses these limitations with an immutable, append-only journal that ensures data integrity and provides complete auditability.
The image discusses the need for QLDB by highlighting issues with traditional databases, such as being mutable, centralized, lacking transparency, having a single point of failure, requiring consensus mechanisms, and concerns about privacy and confidentiality.

​
Overcoming Limitations with the QLDB Journal

In a conventional database structure, data is stored in tables, and every transaction is recorded in a mutable transaction log. While essential for disaster recovery, these logs can be directly modified, compromising data integrity. QLDB replaces this approach with an immutable, append-only journal that records every write operation—whether an insert, update, or delete.
The image is an infographic about Amazon Quantum Ledger Database (Amazon QLDB), highlighting its features: transparency, immutability, and cryptographic verifiability.

​
A Car Lifecycle Example

Imagine using QLDB to track a car’s lifecycle:
  • Initial Entry: The car’s first record is written to the journal as a block containing a unique identifier, metadata, and a hash value. This entry is updated in both the current data table (C table) and the history table (H table).
  • First Resale: When the car is sold to Thomas, a new journal entry is added. The C table reflects the current owner, and the H table records the transaction.
  • Subsequent Resale: When sold to Smith, the process repeats—appending a new block to the journal, ensuring every transaction is recorded chronologically and securely.
Because QLDB’s journal is append-only, every change is permanently recorded. This design guarantees that the full history of the ledger can be queried, as no data is ever altered once committed.
The image compares a traditional database with AWS QLDB, highlighting components like tables, transaction logs, and replay for traditional databases, and a journal with an append-only data structure for QLDB.

​
Ensuring Data Integrity with Cryptographic Verification

QLDB writes one block to its journal per transaction. Each block contains entry objects representing the processed document and the PartiQL statements applied. These blocks are sequenced and cryptographically linked using SHA-256, similar to blockchain technology, to maintain data integrity.
The image illustrates the immutability of AWS QLDB, showing a sequence of operations (insert, update, delete) with corresponding sequence numbers. Each operation is represented by a box with a sequence number, demonstrating the ledger's immutable nature.
Using digest and Merkle audit proofs, QLDB lets you verify that no unauthorized changes have occurred. Each block, containing data documents, metadata, and PartiQL statements, is hashed and chain-linked to ensure a verifiable record.
The image illustrates the cryptographic verification process in AWS QLDB using SHA-256 hash chaining, showing a journal with interconnected blocks containing Amazon Ion documents and metadata.

​
Core Features of QLDB

QLDB brings several powerful features to ledger management:
  • Open-Source and SQL-Compatible Query Language: Utilizes PartiQL which extends SQL to work with Amazon Ion, its document-oriented data model.
  • Fully Managed and Serverless: Eliminates the need for server management while ensuring high availability.
  • ACID Compliant: Supports enterprise-level reliability for mission-critical applications.
The image describes features of AWS QLDB, highlighting its SQL-like flexibility, serverless availability, and enterprise-grade quality.

​
Use Cases for QLDB

QLDB is ideal for applications that demand a verifiable, immutable ledger:
  • Financial Transactions: Track credit and debit card purchases.
  • Supply Chain Management: Document shipments and purchases with an indelible audit trail.
  • Claims History: Maintain an immutable record of insurance or digital claims.
The image shows three use cases for QLDB: Financial Transaction, Supply Chain Systems, and Claim History, each represented with an icon.
Below is a comparison table summarizing the key differences between traditional databases and AWS QLDB:
FeatureTraditional DatabaseAWS QLDB
Data MutabilityMutable records can be updated or deletedImmutable, append-only journal records all changes
TransparencyLimited data traceabilityFull auditability with cryptographically verifiable logs
CentralizationSingle-entity managementCentral trusted authority with complete history preservation
Single Point of FailureVulnerable if the central server failsServerless, highly available architecture
Consensus MechanismAbsentBuilt-in cryptographic hash chaining
Privacy FeaturesBasicSupports advanced privacy measures
Discover further details in the AWS QLDB documentation.

​
Dual Table Structure: Current vs. History

QLDB organizes data using two table types:
  • Current Table (C table): Reflects the latest data state.
  • History Table (H table): Stores an immutable ledger of all historical changes.
This structure allows for rapid access to current data while preserving a comprehensive audit trail.
The image is a summary of Amazon QLDB, explaining its data organization into current and history tables, and highlighting its design for data integrity, transparency, and auditability.

​
Conclusion

Amazon QLDB transforms ledger management through its immutable, highly transparent, and cryptographically verifiable transaction log. With its append-only journal, dual table architecture, and robust verification through SHA-256 hash chaining, QLDB is the ideal solution for applications where data integrity, transparency, and auditability are paramount.

Watch Video