Transaction Interface Decoupling Hierarchical Enterprise Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current transaction management services in enterprise systems, such as those defined by JTA, JTS, and JCA specifications, are hierarchical in nature, leading to low scalability and significant overhead, especially during high load intervals due to the unnecessary generation of coordinator and terminator objects.
Innovation Solution
A transaction interface is introduced within the application server that binds multiple transaction management services and provides a scalable, efficient access method by decoupling these services from their hierarchical interdependence, allowing direct access and reducing redundant object creation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If hierarchical transaction management services (JTA, JTS, JCA) are used, then comprehensive transaction management functionality is provided, but system overhead increases and scalability decreases during high load intervals
Solution Approach 1:
The patent segments the monolithic hierarchical transaction management architecture into independent, parallel service components. Each transaction management service (JTA, JTS, JCA) operates as a separate entity accessible through a unified interface, eliminating the nested hierarchical structure and reducing system overhead while maintaining comprehensive functionality.
Solution Approach 2:
The patent creates a universal transaction interface that provides access to multiple transaction management services simultaneously. This single interface consolidates functionality from JTA, JTS, and JCA services, allowing the system to manage diverse transaction types without requiring separate hierarchical access paths for each service.
2Reliability
If hierarchical transaction management services are used, then comprehensive transaction management functionality is provided, but scalability is reduced during high load intervals
Solution Approach 1:
By dividing the hierarchical architecture into parallel, independent service segments, the system can scale each service component independently. This segmentation allows horizontal scaling during high load intervals without being constrained by the rigid hierarchical structure, thereby improving productivity and scalability while preserving transaction management functionality.
Solution Approach 2:
The patent transitions from a vertical hierarchical dimension to a horizontal parallel dimension. Instead of nesting services in multiple layers (JCA→JTA→JTS), the system arranges services in a flat, parallel structure accessible through a single interface, adding dimensional flexibility that enables better scalability under high load conditions.
3Reliability
If coordinator and terminator objects are generated in hierarchical services, then transaction coordination is achieved, but unnecessary overhead is created
Solution Approach 1:
The patent extracts the essential transaction coordination functionality from the hierarchical service structure and implements it directly through the unified transaction interface. By removing the intermediate coordinator and terminator objects that exist only in the hierarchical implementation, the system achieves transaction coordination with minimal overhead, eliminating unnecessary object creation and destruction cycles.
Solution Approach 2:
The unified transaction interface enables services to coordinate transactions directly without requiring external coordinator objects. Each service can independently manage its transaction state and coordinate with others through the interface, reducing dependency on heavy-weight coordinator and terminator objects and thereby reducing overhead while maintaining coordination reliability.
Data Source
AI summary
A system and method to provide an interface to access transaction management services. The interface is declared and the transaction management services are bound to the interface. The transaction management services provide services for managing related transactions executing on remote nodes in an enterprise system. The transaction management services are published to components of the application server executing on at least one of the remote nodes.