Database Interface Transaction Termination Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current transaction termination methods in Web-based applications incur performance costs due to system latency and resource overhead, particularly when deciding between COMMIT and ROLLBACK methods, as they often require passing commands to the database server and waiting for results, with ROLLBACKs sometimes incurring additional costs by clearing caches and resetting connection states.
Innovation Solution
A database interface that determines whether to send a termination command to the database server and chooses between COMMIT and ROLLBACK based on the current transaction state, deferring configuration of connection parameters until necessary to optimize transaction termination, using a connection handling infrastructure that maintains both actual and desired state information for connection parameters and synchronizes them only when required.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a termination request is sent to the database server to terminate a transaction, then the transaction is properly terminated and data consistency is maintained, but system latency increases due to the round-trip communication and waiting for results
Solution Approach 1:
The patent applies preliminary action by determining the appropriate termination command (COMMIT or ROLLBACK) in advance, before sending it to the database server. The system evaluates the transaction state and decides on the termination command locally, then sends only the necessary command to the server, reducing the time spent in communication and waiting.
Solution Approach 2:
The database interface performs self-service by autonomously determining whether a termination command is needed and which type of command to send, based on the transaction state. This eliminates the need for the application to make these decisions and reduces unnecessary communication with the database server, thereby reducing latency while maintaining reliable transaction termination.
2Reliability
If a ROLLBACK method is called to terminate a transaction, then data consistency is restored, but additional performance costs are incurred due to cache clearing and connection state resetting
Solution Approach 1:
The patent applies preliminary action by evaluating the transaction state before termination and determining whether a ROLLBACK is actually necessary. By assessing the current state in advance, the system can avoid unnecessary ROLLBACK operations that would trigger cache clearing and connection state resetting, thereby maintaining data consistency only when required while improving overall termination efficiency.
Solution Approach 2:
The patent changes the parameter of transaction termination by introducing state-based decision-making. Instead of always executing ROLLBACK or always executing COMMIT, the system dynamically selects the appropriate termination command based on the transaction state parameters, thereby avoiding unnecessary cache clearing and connection state resetting operations while maintaining data consistency.
3Reliability
If the database interface always sends a termination command to the database server, then transaction termination is guaranteed, but system resources are wasted due to unnecessary commands and latency
Solution Approach 1:
The patent applies partial action by sending termination commands to the database server only when necessary, based on the transaction state. Instead of always sending termination commands (excessive action), the system evaluates the state and sends commands only in cases where termination is actually required, thereby guaranteeing transaction termination reliability while reducing system resource usage and avoiding unnecessary latency.
Solution Approach 2:
The database interface performs self-service by autonomously determining whether a termination command is needed based on the transaction state. This intelligent decision-making capability allows the system to guarantee transaction termination only when necessary, eliminating wasteful system resource usage associated with always sending termination commands, while maintaining the reliability guarantee through state-based evaluation.
Data Source
AI summary
Embodiments of the invention are generally directed to a system and method for optimizing transaction termination. A database interface receives an indication to terminate a transaction. The database interface decides whether to send a command to the underlying database server to terminate the transaction. If the database interface does send a command to the database server, it determines which command is appropriate to send.