Multi-Document Transaction Management with Atomicity Control

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Databases with dynamic schemas face challenges in managing multi-document transactions, as conventional operations are limited to single documents, and updating data across multiple documents requires complex operations that can fail partially, leading to inconsistent database states.

Innovation Solution

A database system and method that enables multi-document transactions by generating a transaction identifier, associating operations with it, performing transactions on multiple documents, and ensuring either all or none of the operations are committed, with error handling and reversal mechanisms to maintain atomicity and consistency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multi-document transactions are implemented in databases with dynamic schemas, then data consistency and integrity across multiple documents are improved, but system complexity and operational difficulty increase

Engineering Contradiction:

Improvedata consistencyVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the multi-document transaction processing into distinct phases: transaction initiation, operation execution on individual documents, commit coordination, and rollback preparation. Each phase handles specific tasks independently, managing complexity through structured division of the transaction workflow across multiple documents while maintaining overall consistency.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces intermediary components including transaction logs that record operations across documents, commit coordination mechanisms that mediate between multiple document operations, and rollback management systems that act as intermediaries to reverse operations if needed. These intermediaries simplify the complexity of direct multi-document coordination.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If all-or-nothing transaction execution is enforced across multiple documents, then data integrity is improved, but operational flexibility and ease of implementation worsen

Engineering Contradiction:

Improvedata integrityVSAvoidoperational flexibility

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary actions by logging all intended operations before actual execution, preparing rollback information in advance, and establishing commit coordination mechanisms prior to document modifications. This preliminary preparation enables the all-or-nothing constraint to be enforced automatically without requiring complex real-time coordination during operation execution.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms through transaction logs that record the state of each document operation, commit status tracking that provides feedback on transaction progress, and error detection systems that signal when operations fail. This feedback enables automatic rollback decisions and maintains operational flexibility while ensuring data integrity through structured feedback loops.

Inventive Principle:

Principle #23Feedback

3Reliability

If transaction operations are replicated across multiple storage nodes, then database availability and robustness are improved, but transaction coordination complexity and time consumption increase

Engineering Contradiction:

Improvedatabase availabilityVSAvoidtransaction coordination time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The transaction coordination is segmented into independent operations that can be executed in parallel across multiple storage nodes. Each node processes its assigned document operations independently while the coordination mechanism manages only the essential synchronization points (commit/rollback decisions), reducing overall coordination time compared to sequential processing.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent uses copying mechanisms by replicating transaction logs and operation records across multiple storage nodes. This copying enables parallel processing of transaction operations while maintaining consistency through replicated state information, reducing coordination time by allowing simultaneous operation execution rather than sequential processing.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS11768885B2Systems and methods for managing transactional operation

Publication Date: 2023.09.26 MONGODB INC

AI summary

Described herein are embodiments of a database system for performing multi-document transactions. The database system comprises a database comprising a plurality of data storage nodes. The database system receives transactions that access at least two documents stored in the database. The database system generates a transaction identifier associated with the transaction and associates operations in the transaction with the transaction identifier. The database system performs at least part of the transaction on the database and determines whether an error occurred in performing in performing the transaction. When the database system determines that an error occurred in performing the transaction, the database system reverses any performed operations of the transaction. When no error occurs in performing the transaction, the database system outputs a confirmation.