Self-Described Data Sharing Across Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data exchange mechanisms between applications face challenges due to differences in data formats and semantics, requiring pre-existing knowledge and adapters that disrupt communication when changes occur, limiting dynamic interaction and adaptability across multiple services.
Innovation Solution
A method for sharing self-described data across services by organizing data into element groups with schema identity information, allowing messages to be sent in an unbounded sequence, enabling applications to operate without disruption even when data formats change, and supporting multiparty communication without pre-existing knowledge of supported formats or semantics.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If adapters are used to enable communication between applications with different data formats, then data exchange is enabled, but system complexity increases and adaptability decreases when changes occur
Solution Approach 1:
The patent introduces a message broker as an intermediary component that receives messages from publishers and distributes them to subscribers. The broker handles format conversion and routing, eliminating the need for direct adapter pairs between every application combination. This mediator approach reduces overall system complexity while maintaining adaptability to different data formats through standardized message structures.
Solution Approach 2:
The system segments data exchange into independent publish-subscribe pairs, where each application can independently publish or subscribe to specific data types. This segmentation allows individual components to be modified without affecting others, improving adaptability to format changes while reducing the complexity of inter-component adapters.
2Ease of operation
If pre-existing knowledge of peer data definitions is required for communication, then accurate data exchange is achieved, but flexibility and ease of operation deteriorate when new applications are added
Solution Approach 1:
The message broker automatically performs data validation, format conversion, and routing based on predefined schemas and message types. Applications don't need to manually configure knowledge about peer data definitions - the broker handles this self-service functionality, making it easy to add new applications while maintaining accurate data exchange through automated validation and conversion.
Solution Approach 2:
Data schemas, validation rules, and conversion logic are pre-configured in the message broker before runtime. This preliminary setup enables the system to automatically handle new applications and data formats without requiring real-time configuration or manual knowledge sharing between applications, improving ease of operation while preventing information loss through automated validation.
3Reliability
If adapters are modified to accommodate changes in one application, then communication accuracy is maintained, but productivity and time efficiency decrease due to required maintenance
Solution Approach 1:
The message broker serves multiple functions simultaneously: validation, conversion, routing, and error handling. This universal component handles all adaptational needs for multiple applications through a single system, maintaining communication reliability across all applications while eliminating the need to modify multiple individual adapters, thus improving maintenance productivity.
Solution Approach 2:
The system employs dynamic message routing and format conversion based on real-time message types and subscriber requirements. The broker can adaptively route messages to appropriate subscribers and perform on-the-fly format conversions, maintaining communication reliability without requiring static adapter configurations that need manual updates when applications change.
4Adaptability or versatility
If data is organized into element groups with schema identity information, then self-described data sharing is enabled, but message structure complexity increases
Solution Approach 1:
The message structure uses nested element groups where data is organized in hierarchical layers with schema identity information embedded at each level. This nesting allows messages to be self-described with embedded schema references while maintaining a manageable structure through recursive organization, enabling adaptability without overwhelming complexity.
Solution Approach 2:
The patent adds a schema identity dimension to the message structure, allowing data to be described by reference to external schema definitions rather than embedding complete validation logic within the message. This dimensional addition enables self-described data capability while keeping message structures concise by referencing schemas separately, reducing embedded complexity.
Data Source
AI summary
In accordance with one embodiment of the present invention, there are provided mechanisms and methods for sharing data across services. These mechanisms and methods for applications to share information even when the applications use different data formats make it possible for business services to operate without any disruption even if the input data stream produced by it's peer business service has been changed.