Database Dispatcher for Task Routing and Feature Availability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database systems face challenges in efficiently dispatching tasks between the application layer and the database layer, particularly in materials requirements planning, where determining the availability of features in the database layer is complex, leading to difficulties in performance and resource allocation.
Innovation Solution
A method and system that analyze tasks to determine if all required features are implemented in the database layer, dispatching tasks to the database for processing if available, and to the application layer if not, optimizing task distribution and resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If tasks are dispatched to the database layer for processing, then database performance is improved, but determining feature availability becomes more complex
Solution Approach 1:
The system pre-generates and stores feature capability information in a feature information data structure during database initialization or schema definition. This preliminary action allows the dispatcher to quickly determine feature availability without complex runtime analysis, resolving the contradiction by preparing information in advance that simplifies subsequent dispatch decisions.
Solution Approach 2:
The patent introduces a dispatcher module as an intermediary between the application layer and database layer. This dispatcher contains a feature information data structure that acts as a mediator, storing pre-analyzed capability information. The dispatcher uses this intermediate representation to make informed routing decisions, simplifying the complexity of determining whether to execute tasks in the database or application layer.
2Productivity
If stored procedures are used in the database layer, then performance is enhanced, but development and testing becomes more difficult
Solution Approach 1:
The dispatcher module serves as an intermediary that abstracts the complexity of stored procedure usage from developers. By maintaining a feature information data structure that documents which database features are available, the system allows developers to write application layer code without needing to understand or manage the complexity of stored procedures. The dispatcher automatically routes appropriate tasks to the database layer when features are available, preserving performance benefits while simplifying development.
Solution Approach 2:
The system segments the decision-making process into two independent parts: (1) the database layer with its optimized stored procedures, and (2) the application layer with simplified development. The feature information data structure acts as a segmentation interface, allowing each layer to operate independently at its optimal complexity level while maintaining overall system performance.
3Ease of operation
If tasks are dispatched to the application layer, then development simplicity is maintained, but computational resources increase
Solution Approach 1:
The dispatcher module with its feature information data structure acts as an intelligent intermediary that automatically makes optimization decisions. Developers can maintain simple application layer code while the dispatcher monitors feature availability and automatically routes computationally intensive tasks to the database layer when appropriate. This eliminates the need for developers to manually optimize resource usage while still achieving reduced computational resource consumption through intelligent task routing.
Data Source
AI summary
Example methods and systems are directed to dispatching database tasks. An application may access data associated with a task. The data may indicate features (e.g., processing functionality) that will be used to complete the task. The application may determine whether all such features are implemented in the database layer. The application may dispatch the task to the database layer if all features are implemented therein. The application may perform the task in the application layer if one or more of the features are not available in the database layer. In some example embodiments, the task involves materials requirements planning. Such a task may include determining, for a given bill of materials (“BOM”), the quantity of materials available on-hand, the quantity available from suppliers, the transport or delivery time for the various quantities, and other data regarding the BOM.