Global Transaction Identifier Sharing in Middleware

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Transactional middleware systems face challenges in optimizing performance across multiple transaction domains and ensuring data consistency and integrity, particularly in handling global transactions and read-only operations.

Innovation Solution

The system supports tightly-coupled and loosely-coupled global transactions by using a common global transaction identifier (GTRID) and composite branch qualifiers, enabling data sharing and optimizing read-only operations through the two-phase commit protocol and read-only optimization techniques, while maintaining ACID properties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If a common global transaction identifier (GTRID) is shared across multiple transaction domains, then transaction processing efficiency is improved and data sharing is maximized, but maintaining data consistency and integrity across domains becomes more challenging

Engineering Contradiction:
Improvetransaction processing efficiencyVSAvoiddata consistency and integrity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the global transaction identifier into multiple components including domain-specific identifiers and branch qualifiers. This segmentation allows each transaction domain to maintain its own data consistency rules while participating in a unified global transaction, thus resolving the contradiction between efficiency and consistency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a transaction coordinator as an intermediary that manages the common GTRID across multiple domains. This coordinator ensures that data consistency and integrity are maintained while allowing efficient transaction processing by mediating between the need for shared identifiers and domain-specific consistency requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If read-only optimization techniques are used to improve performance, then transaction processing speed is enhanced, but the complexity of ensuring ACID properties across distributed domains increases

Engineering Contradiction:
Improvetransaction processing speedVSAvoidcomplexity of ensuring ACID properties
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent applies local quality by allowing different transaction domains to have different optimization levels. Read-only domains can use simplified protocols for speed, while domains requiring data modification maintain full ACID compliance, thus enhancing performance without universally increasing complexity.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements partial action by applying read-only optimization only where appropriate. Not all transaction domains require full two-phase commit protocols, so the system applies optimization selectively to read-only domains while maintaining full ACID properties where needed, reducing overall complexity.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If multiple transaction domains use different global transaction identifiers, then data consistency within each domain is maintained, but transaction processing efficiency and data sharing across domains deteriorates

Engineering Contradiction:
Improvedata consistency within domainVSAvoidtransaction processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges multiple domain-specific identifiers into a unified common global transaction identifier structure. This combination allows the system to maintain the consistency benefits of domain-specific identifiers while achieving the efficiency and data sharing benefits of a unified identifier across all domains.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10289443B2System and method for sharing global transaction identifier (GTRID) in a transactional middleware environment
Publication Date: 2019.05.14 ORACLE INT CORP
  • US10289443B2 patent drawing
  • US10289443B2 patent drawing
  • US10289443B2 patent drawing

AI summary

A system and method can support a tightly-coupled global transaction. One or more transaction servers operate to span the global transaction with a plurality of branches across a plurality of transaction domains, wherein each said branch is associated with an individual branch qualifier, and each said transaction domain is associated with a different global transaction identifier (GTRID). Furthermore, the transaction servers can configure the plurality of branches in the global transaction to share a common global transaction identifier (ID), and associate a composite branch qualifier with at least one branch of the global transaction in a transaction domain, wherein the composite branch qualifier includes a global transaction identifier (GTRID) that is associated with the transaction domain and an individual branch qualifier that is associated with the at least one branch.