Modular Transaction Scheduler for Flexible Path Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing transaction processing systems are monolithic, rigidly architected, and overly complicated, leading to brittleness, error-proneness, and difficulty in adapting to new functionalities without extensive regression testing.
Innovation Solution
Decompose monolithic transaction processing systems into discrete functional components, allowing for flexible and reliable server architectures that support parallelism, roll-back and roll-forward features, and improved load balancing through components like a web site, application launcher, and orchestrator.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If monolithic transaction processing systems are used, then system stability is maintained, but flexibility and adaptability deteriorate
Solution Approach 1:
The patent divides the monolithic transaction processing system into discrete, independent components including transaction path definitions, step definitions, program logic modules, and data access components. Each component can be independently modified, deployed, and maintained without affecting the entire system, thereby improving flexibility while managing complexity through modular organization.
2Reliability
If monolithic transaction processing systems are used, then implementation simplicity is maintained, but reliability deteriorates
Solution Approach 1:
By segmenting the system into isolated transaction paths and steps with defined interfaces, the patent enables independent testing and validation of individual components. This segmentation reduces single points of failure and improves reliability while the standardized architecture patterns manage the inherent complexity.
Solution Approach 2:
The patent introduces intermediary components such as transaction path definitions and step definition layers that act as mediators between the user interface and core processing logic. These intermediaries provide standardized interfaces and abstraction layers that improve reliability by isolating failures while managing system complexity through structured communication protocols.
3Productivity
If monolithic transaction processing systems are used, then initial development speed is maintained, but future adaptation speed deteriorates
Solution Approach 1:
The patent implements segmentation by creating independently deployable transaction paths and steps that can be modified without requiring system-wide changes. This allows rapid adaptation to new requirements by adding or modifying individual paths while maintaining existing functionality, significantly improving adaptation speed while the modular structure manages modification complexity.
Solution Approach 2:
The patent introduces dynamic configuration capabilities where transaction paths and steps can be defined and modified at runtime through configuration files or databases rather than requiring code compilation and deployment. This dynamic approach enables rapid adaptation to changing requirements while managing complexity through configuration management rather than code management.
4Loss of time
If monolithic transaction processing systems are used, then testing scope is minimized, but regression testing burden increases
Solution Approach 1:
By segmenting the system into independent transaction paths and steps, the patent enables isolated testing of individual components without requiring full system regression testing. Each path and step can be tested independently, and the modular architecture ensures that changes in one component do not require retesting of unrelated components, reducing testing time while managing complexity through structured test organization.
Data Source
AI summary
An implementation may involve: receiving, by a web site, selection of a server application, wherein the server application is associated with a path, wherein the path includes a set of steps, wherein the set of steps is associated with program logic to perform a set of functions; receiving, by an application launcher, a request on behalf of a client device; determining, by the application launcher, the server application based on the request, and also based on metadata that relate to the server application and an operator of the web site; providing, by the application launcher, a client application to the client device, the client application configured to interact with the server application; executing, by an orchestrator, the path, wherein at least some of the set of steps include interaction with an external service, wherein a context of the execution is written in a database between execution of some of the steps.


