Transaction Service Synchronization via Callback Queues
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems are limited in synchronizing transactions across multiple platforms, particularly lacking support for callback capabilities and only allowing synchronous and asynchronous transactions.
Innovation Solution
Implementing a single transaction service on a primary platform that manages all transaction executions and synchronizations, with callback services on all platforms, supporting synchronous, asynchronous, and callback transaction types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single transaction service manages all transaction executions on a primary platform, then transaction synchronization across multiple platforms is improved, but system complexity increases
Solution Approach 1:
The system segments transaction management into two distinct components: a transaction service on the primary platform that handles transaction execution and result generation, and callback services on all platforms that handle result distribution. This segmentation allows centralized transaction control while distributing the callback handling, reducing the complexity burden on any single component.
Solution Approach 2:
The patent introduces a callback service as an intermediary component that mediates between the transaction service and client devices. The callback service receives transaction results from the primary platform and distributes them to appropriate clients, acting as a buffer that simplifies the interaction model and reduces direct complexity in the transaction service.
2Reliability
If dynamic queuing is implemented for transaction requests, then transaction execution control is improved, but processing time increases
Solution Approach 1:
The transaction service performs preliminary actions by evaluating incoming transaction requests against the execution status of ongoing transactions before queuing them. This preliminary evaluation ensures that transactions are only queued when necessary, avoiding unnecessary delays while maintaining proper execution control.
Solution Approach 2:
The queuing mechanism is dynamic rather than static, allowing the system to adaptively decide whether to queue a transaction based on real-time execution status. This dynamic approach ensures that transactions are queued only when execution control requirements demand it, minimizing processing time delays while maintaining reliability.
3Productivity
If callback services are deployed on all platforms, then real-time result notification capability is improved, but system complexity increases
Solution Approach 1:
The callback service is designed as a universal component that can be deployed on any platform with the same standardized interface and functionality. This multi-functionality allows the same service to operate across different platforms without requiring platform-specific implementations, reducing overall system complexity while enabling real-time notifications.
Solution Approach 2:
The system changes the parameter of service deployment from centralized to distributed across platforms. By standardizing the callback service parameters and interfaces, the system enables real-time notifications on all platforms without proportionally increasing complexity, as each instance operates independently with the same standardized behavior.
Data Source
AI summary
Synchronizing middleware process execution on multiple platforms with callback capabilities includes receiving, by a first computing platform of a system, a first request for execution of a first transaction associated with execution of a process from a first client device, the first computing platform including a transaction service, receiving, by the first computing platform, a second request for execution of the first transaction, from a second client device, and queuing, by the transaction service, the first request and the second request for the transaction. The first computing platform determines, based on an execution status of the first transaction, whether to associate a result of the first transaction with the second request.