Non-Invasive Transaction Tracking via Message Queue Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current business systems face challenges in tracking transactions across multiple steps without being invasive to existing application modules and messaging systems, as they require duplicate message generation and code modifications, which interrupt processing.
Innovation Solution
A tracking system integrated with a messaging system that includes a tracking module to extract and store status data from message queues, allowing for non-invasive tracking without modifying application modules or interrupting messaging software operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If application modules generate duplicate messages with state information to feed a tracking application, then tracking capability is improved, but device complexity and code requirements increase
Solution Approach 1:
The tracking functionality is extracted from the application modules and placed in a separate tracking application that consumes messages from the messaging system. The tracking module independently generates tracking messages by subscribing to message queues and extracting status data, eliminating the need for application modules to include tracking code.
Solution Approach 2:
A tracking module acts as an intermediary between the messaging system and the tracking application. It subscribes to message queues, processes messages, generates tracking messages with status information, and sends them to the tracking application, thereby decoupling the tracking functionality from the business application modules.
2Reliability
If application modules request messaging software to generate report messages with state information, then tracking capability is improved, but processing efficiency deteriorates due to interruptions
Solution Approach 1:
The tracking module continuously subscribes to and processes messages from the messaging queues without interrupting the messaging software's normal operation. The messaging system continues to process business messages while the tracking module independently generates tracking messages in parallel, maintaining continuous useful action in both systems.
Solution Approach 2:
The tracking module autonomously generates tracking messages by subscribing to message queues and processing messages itself, without requiring the messaging software to be interrupted or to generate report messages. The tracking system serves itself by independently extracting status data and creating tracking messages.
3Reliability
If messaging software is interrupted to request generation of report messages, then tracking capability is improved, but system stability deteriorates
Solution Approach 1:
The tracking message generation function is extracted from the messaging software and implemented in a separate tracking module. This allows the messaging software to continue processing business messages without interruption while the tracking module independently generates tracking messages, maintaining system stability.
Solution Approach 2:
The tracking module serves as an intermediary that subscribes to message queues and generates tracking messages without requiring the messaging software to be interrupted. This decoupling maintains the stability of the messaging system while enabling tracking functionality.
Data Source
AI summary
A tracking system includes a business system using a plurality of application modules each including a computer for processing a transaction including a plurality of steps. A messaging system includes a messaging computer program embodied in a computer readable medium in each of the computers for communicating between the computers. The messaging system generates queues of messages being communicated between the computers. The messaging system can be configured by an administrator to generate tracking data about the messages being communicated between the computers. A tracking module is included in one of the computers, and has the messaging computer program and a tracking computer program embodied in the computer readable medium for specifying status data for retrieval from the messaging queues, receiving the status data from the messaging queues into a tracking queue, and storing the status data in a data storage system.