Generic Data Container for Asynchronous Interface Extensions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a distributed business systems landscape, unilateral interface changes across different software versions can lead to communication failures between systems with incompatible interfaces, necessitating cumbersome process-oriented field extensibility and either simultaneous or no upgrades across the landscape.
Innovation Solution
A method that involves receiving data objects with additional features at a first software component's inbound interface, storing characteristic information in a generic data container, and reconstructing the data object upon upgrading to a newer version, allowing seamless communication with components on different versions by recreating and mapping the additional features.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a software component is upgraded to a newer version with enhanced interfaces, then the component gains access to additional data features and improved functionality, but communication failures occur with other systems that have not been upgraded and still use older interface versions
Solution Approach 1:
The system performs preliminary actions by storing characteristic information of additional data features in a generic data container before the upgrade. When communication with older systems is needed, the system proactively reconstructs data objects by retrieving this stored information and combining it with data from internal data structures, ensuring compatibility is prepared in advance rather than reacting to communication failures
Solution Approach 2:
The generic data container acts as an intermediary between the upgraded component's internal data structures and the older interface versions. It stores characteristic information about additional features in a neutral format that can be selectively reconstructed into data objects compatible with either newer or older systems, mediating the interface incompatibility without requiring changes to the upgraded component itself
2Adaptability or versatility
If process oriented field extensibility is used to handle interface changes, then communication between systems with different interface versions can be maintained, but the approach becomes cumbersome and requires action for any system as soon as another system undergoes an interface change
Solution Approach 1:
The system merges the handling of standard data features and additional data features into a unified data object structure. The generic data container stores characteristic information that can be combined with internal data structure information during reconstruction, creating a single integrated approach that handles both interface versions simultaneously rather than requiring separate processing paths for different interface scenarios
Solution Approach 2:
The system implements self-service by automatically reconstructing data objects when needed without requiring external intervention or manual configuration. The generic data container is automatically populated with characteristic information, and the reconstruction process occurs transparently based on the communication partner's interface version, eliminating the need for manual field extensibility actions whenever interface changes occur
3Reliability
If all systems in a networked landscape are upgraded simultaneously to maintain interface compatibility, then communication reliability is maintained, but the complexity and cost of coordinating simultaneous upgrades across multiple systems becomes prohibitive
Solution Approach 1:
The system segments the interface compatibility problem by separating additional data features from standard data features. The generic data container stores characteristic information about additional features independently, allowing the upgraded component to maintain communication with older systems by selectively reconstructing data objects with only the necessary features, rather than requiring all systems to be upgraded together as a monolithic unit
Data Source
AI summary
A data object can be received at a first time at a first inbound interface of a first software component from a second software component. The first inbound interface can be configured to map a first feature of the data object to at least one first internal data structure of the first software component but not configured to map a second data feature of the data object to any corresponding internal data structure of the first software component. Characteristic information of the second data feature can be stored in a generic data container added to the internal data structure. The characteristic information can include a value of the second data feature and metadata describing an identifier of the second data feature. A reconstructed data object can be formed at a second time subsequent to the first time. Related methods, systems, and articles of manufacture are disclosed.