Dynamic Transaction Coordinator Selection in Middleware
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multitier hybrid transaction processing middleware systems, there is no known method to dynamically determine the optimal transaction coordinator for each transaction instance, leading to suboptimal transaction resolution and increased processing time.
Innovation Solution
A method where the transaction processing middleware coordinator receives and compares weightages of participating TPMs, and if a participant's weightage is higher, it dynamically changes the coordinator function to that participant, enabling better transaction resolution optimization by selecting the most capable TPM as the interim coordinator.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a fixed transaction coordinator is used in multitier hybrid transaction processing middleware systems, then the system structure is simple and easy to implement, but the transaction resolution efficiency is suboptimal and processing time is increased
Solution Approach 1:
The patent implements dynamic coordinator selection by introducing weightage parameters that are calculated and updated based on current system state and transaction characteristics. The coordinator is selected dynamically for each transaction instance rather than being fixed, allowing the system to adapt to changing conditions and optimize transaction resolution efficiency.
Solution Approach 2:
The patent changes the parameter of coordinator selection from a static configuration to a dynamic parameter-based selection mechanism. Weightage parameters are computed considering multiple factors including transaction type, participant capabilities, and system load, enabling flexible and optimized coordinator assignment for each transaction.
2Speed
If the transaction coordinator dynamically changes based on weightage comparison, then the transaction resolution efficiency is enhanced and processing speed is improved, but the coordination overhead and system complexity increases
Solution Approach 1:
The patent performs preliminary weightage calculation and coordinator determination before transaction execution begins. By pre-computing the weightages of potential coordinators and identifying the optimal coordinator in advance, the system avoids runtime complexity while achieving fast transaction processing.
Solution Approach 2:
The patent introduces weightage parameters as an intermediary mechanism that mediates between multiple potential coordinators and the transaction. This intermediary calculation layer simplifies the decision-making process by providing a clear quantitative basis for coordinator selection, reducing the complexity of direct coordinator evaluation.
3Productivity
If the TPM coordinator keeps coordinating despite having lower weightage, then the coordinator role remains stable, but unnecessary transaction flows increase and resolution efficiency decreases
Solution Approach 1:
The patent inverts the traditional assumption that the initiating TPM should always be the coordinator. Instead, it inverts the selection criterion to choose the TPM with the highest weightage, regardless of whether it initiated the transaction. This inversion eliminates unnecessary transaction flows by directly assigning coordination to the most capable TPM.
Solution Approach 2:
The patent implements a feedback mechanism where weightage information is communicated back to the transaction initiating TPM, enabling it to identify and transfer coordinator role to the appropriate TPM. This feedback loop ensures that transactions are routed through the optimal coordinator, reducing unnecessary flows and improving resolution efficiency.
Data Source
AI summary
A technique relates to dynamically determining a transaction coordinator. A transaction processing middleware (TPM) coordinator receives TPM weightages of TPM participants, where the TPM coordinator has a TPM coordinator weightage, and where the TPM coordinator and TPM participants are executing a transaction instance. The TPM coordinator individually compares the TPM coordinator weightage to each of the TPM weightages of the TPM participants. In response to not one of the TPM weightages of the TPM participants being greater than the TPM coordinator weightage, the TPM coordinator is kept unchanged. In response to a given TPM weightage of the TPM weightages of the TPM participants being greater than the TPM coordinator weightage, the TPM coordinator changes a TPM coordinator function to a given TPM participant having the given TPM weightage such that the given TPM participant is an interim TPM coordinator for the transaction instance.