Software Bus Dynamic Message Evaluation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional software buses are limited to handling static data and events, lacking the ability to process dynamic data and perform actions based on up-to-date information, which restricts their flexibility and functionality in modern service-oriented architectures.
Innovation Solution
The implementation of dynamic messages with executable code embedded in the message data, allowing services to access and process dynamic data and perform actions even if the data did not exist at the time of message submission, using a software bus that supports evaluation and execution of this code to retrieve and generate data contemporaneously.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional software buses handle only static data, then system simplicity is maintained, but flexibility and functionality are restricted
Solution Approach 1:
The patent applies dynamics by enabling the software bus to handle both static and dynamic data. Event objects now contain executable code that can be evaluated at runtime, allowing the system to adapt to changing conditions and access up-to-date data from external sources, transforming a static architecture into a dynamic one that can respond to real-time changes.
Solution Approach 2:
The patent changes the fundamental parameter of data from static to dynamic by introducing executable code within event objects. This code can execute data retrieval operations that access external sources at runtime, fundamentally altering how data is handled in the system from fixed values to dynamically generated values.
2Productivity
If dynamic data retrieval is implemented, then real-time processing capability is improved, but system complexity increases
Solution Approach 1:
The patent applies self-service by enabling event objects to autonomously retrieve their own data from external sources through embedded executable code. The event objects self-evaluate and self-populate with current data without requiring external intervention, achieving real-time data retrieval while maintaining system autonomy.
Solution Approach 2:
The executable code within event objects acts as an intermediary between the static event structure and dynamic external data sources. This intermediary enables real-time data retrieval by bridging the gap between the message bus architecture and external data systems without requiring fundamental architectural changes.
3Adaptability or versatility
If services are decoupled from data, then system modularity is improved, but data access complexity increases
Solution Approach 1:
The patent applies the nested doll principle by embedding executable code within event objects, which are themselves part of the software bus architecture. This nested structure allows services to remain decoupled from data while the embedded code provides the necessary data access capabilities, creating layers of abstraction that hide complexity.
Solution Approach 2:
The executable code within event objects provides universal data access functionality that works across different services and data sources. This multi-functional approach allows the same mechanism to handle various data retrieval scenarios, reducing overall system complexity despite service decoupling.
Data Source
AI summary
Provided are methods of providing dynamic messages on a software bus. Such methods may include generating a dynamic message that corresponds to a service request from an application that is connected to a software bus. The dynamic message includes an executable portion that is executed to perform an action. The dynamic message is submitted to the bus for execution at a time after submission.