Unit of Work Repository for Stateless Database Commit Rollback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
NoSQL environments, being stateless and non-persistent, lack the commit/rollback functionality present in traditional SQL databases, making it difficult to manage database requests in a way that allows for transaction grouping and error handling.
Innovation Solution
Implementing a system that generates a unique identification code for a unit of work set, allowing database requests to be recorded and committed or rolled back as a logical unit, even across multiple sessions, by using a unit of work repository to manage these requests in a stateless non-persistent computing environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If NoSQL environments use stateless non-persistent connections, then dynamic resource allocation and multi-user access are improved, but commit/rollback functionality is lost
Solution Approach 1:
The patent introduces a unit of work repository as an intermediary mechanism between the stateless connection and the database. This repository persists unit of work sets even when connections are terminated, enabling commit/rollback functionality without requiring persistent connections. The repository acts as a mediator that maintains transactional integrity across stateless interactions.
Solution Approach 2:
The system performs preliminary actions by creating and storing unit of work sets in the repository before database operations are executed. These unit of work sets are prepared in advance with all necessary modifications, allowing them to be committed or rolled back later without requiring the original connection to remain open. This enables transactional control in stateless environments.
2Loss of energy
If connections are terminated after each request, then resource efficiency is improved, but transaction grouping becomes impossible
Solution Approach 1:
The patent segments database requests into discrete unit of work sets, each associated with a unique unit of work token. This segmentation allows individual transactions to be grouped and managed independently, enabling commit/rollback operations even when connections are terminated between requests. Each unit of work set can be tracked and controlled separately in the repository.
Solution Approach 2:
The unit of work repository serves as an intermediary that maintains transactional context across connection terminations. It stores unit of work sets and their associated tokens, enabling the system to regroup and manage transactions even when the original client connection is closed. This mediator preserves transactional integrity without requiring persistent connections.
3Productivity
If modifications are applied immediately to the database, then data availability is improved, but ability to undo modifications is reduced
Solution Approach 1:
The system performs preliminary actions by recording all database modifications in unit of work sets before they are actually applied to the database. These unit of work sets contain the complete set of changes that can be reviewed and decided upon. This allows the system to maintain data availability while preserving the ability to undo modifications by simply rolling back the unit of work set.
Solution Approach 2:
The patent implements beforehand cushioning by creating unit of work sets that buffer modifications before they reach the database. These unit of work sets act as a cushion or buffer layer, allowing modifications to be prepared and stored temporarily. If a rollback is needed, the system can undo all modifications in the unit of work set without affecting the database, thus preserving the ability to repair or undo changes.
Data Source
AI summary
Systems, methods, and computer-readable storage media for processing database requests on a database hosted on a stateless, non-persistent computing environment are provided. A server stores database requests to insert update or delete data in a unit of work set identified by a unique code. The database requests are performed on the database upon receiving an instruction to commit the database requests to the database. If an instruction is sent to rollback a unit of work set the database remains unchanged. This allows a client to handle requests in logical groups.


