WS-AT Affinity Routing via XML Gateway Transaction ID
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web Service Atomic Transaction (WS-AT) systems in large-scale environments often experience deadlock due to multiple service providers attempting to access the same resources simultaneously, leading to delays, connection time-outs, and increased network traffic.
Innovation Solution
Implementing affinity routing within WS-AT systems by using an XML gateway to identify transaction IDs in messages and routing them to specific service providers, ensuring all requests from a client transaction are routed to the same provider, thereby preventing deadlock.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple service providers operate independently in a large-scale WS-AT system, then service provider availability and load distribution are improved, but deadlock occurs when service providers simultaneously access the same resources
Solution Approach 1:
The patent introduces a networking device as an intermediary that sits between clients and service providers. This intermediary maintains a routing table that tracks which service provider is handling which transaction. When a transaction message arrives, the networking device checks the routing table and forwards the message to the appropriate service provider, preventing simultaneous access to the same resource by multiple providers and thus avoiding deadlock while maintaining system availability
2Adaptability or versatility
If service providers are distributed across the network, then system scalability is improved, but connection time-outs and delays increase due to deadlock
Solution Approach 1:
The patent implements preliminary action by pre-establishing the routing table that maps transactions to service providers before any deadlock can occur. The networking device proactively tracks and records which service provider is handling each transaction, so when messages need to be routed, the correct provider is immediately identified without causing delays or time-outs
3Productivity
If service providers handle transactions independently, then processing efficiency is improved, but network traffic increases due to resubmitted requests from deadlocks
Solution Approach 1:
The patent implements feedback through the routing table that continuously tracks the state of transactions and service provider assignments. The networking device uses this feedback information to make intelligent routing decisions, ensuring messages are directed to the correct service provider without causing deadlocks that would require request resubmission and generate additional network traffic
Data Source
AI summary
A method of operating a web service atomic transaction (WS-AT) system includes: receiving, at a processor of an extensible markup language (XML) gateway, a first message from a communicatively coupled client, and inserting a WS-AT Transaction Identifier (ID) from a Simple Object Access Protocol (SOAP) header into a hypertext transfer protocol (HTTP) header of the first message to generate a first modified message. The method also includes: receiving, at a processor of a network device communicatively coupled to the XML gateway, the first modified message from the XML gateway, determining that the WS-AT Transaction ID is not yet associated with a service provider in a routing table, and in response, sending the first modified message to a particular service provider and associating the WS-AT Transaction ID with the particular service provider in the routing table such that future messages from the client can be routed to the particular service provider.