Distributed Database Transaction Validation via Client-Side Digest

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed database management systems face challenges in ensuring the integrity and atomicity of transactions due to commands being received out of order or not received at all, which compromises the reliability of data storage and retrieval.

Innovation Solution

A distributed database system computes a digest of transactions based on command signatures, comparing it with a client-computed digest to validate the order and completeness of commands, ensuring that either all commands are successfully executed or the transaction is rolled back.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If commands are transmitted separately in a distributed database system, then the system can operate with higher flexibility and distribution, but commands may be received out of order or not received at all, compromising transaction integrity

Engineering Contradiction:
Improvedistribution flexibilityVSAvoidtransaction integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by computing a digest of the transaction on the client side before transmitting commands to the database. This digest serves as a pre-computed verification value that enables the database to later validate whether all commands were received in the correct order without requiring complex coordination between distributed nodes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback by having the database compute the same digest independently after receiving all commands and comparing it with the client-computed digest. This feedback mechanism confirms that commands were transmitted and received correctly, allowing the system to detect and reject transactions with missing or out-of-order commands.

Inventive Principle:
Principle #23Feedback

2Reliability

If the system validates transaction integrity by computing and comparing digests, then transaction reliability is improved, but the computational overhead and processing time increase

Engineering Contradiction:
Improvetransaction integrityVSAvoidvalidation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces complex mechanical verification mechanisms with cryptographic hash functions. Instead of requiring the database to track and verify the order and completeness of individual commands through complex state management, it substitutes this with a mathematical digest computation that inherently encodes all necessary verification information.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent transforms the verification problem from checking individual command parameters (order, presence) into a single digest parameter comparison. By changing the verification approach from multiple parameter checks to a single hash value comparison, the system reduces validation complexity while maintaining reliability.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If the system performs digest computation and comparison for every transaction, then transaction validation accuracy is improved, but processing speed decreases

Engineering Contradiction:
Improvevalidation accuracyVSAvoidtransaction processing speed
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent performs the digest computation on the client side before transaction submission, moving part of the computational workload away from the database server. This preliminary action allows the database to receive pre-validated transaction data, reducing the processing burden during transaction execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses cryptographic hashing to create a compact copy (digest) of the entire transaction that can be quickly computed and compared. This copying approach allows for rapid validation without requiring the database to re-process or re-analyze the original command data, thus maintaining high processing speed while ensuring validation accuracy.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11748328B1Distributed database transaction validation
Publication Date: 2023.09.05 AMAZON TECH INC
  • US11748328B1 patent drawing
  • US11748328B1 patent drawing
  • US11748328B1 patent drawing

AI summary

A distributed database receives a first command and second command sent by a client for processing in the context of a transaction. The distributed database validates the transaction by computing a digest based on signatures of the first and second commands, and comparing the computed digest to a digest received from the client. The transaction is committed upon validation.