Multi-Client Persistence Segmentation for Extension Nodes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-client systems, existing technologies lack methods to efficiently isolate and retrieve client-specific extension field values for business data objects, leading to resource inefficiencies and slower data access.
Innovation Solution
Separate storage of standard and extension field values in distinct persistence units, with the extension node instance key and its relation to the standard node instance key stored in a separate unit, allowing for client-specific extension field definitions and faster data retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If extension field values are stored in the same persistence unit as standard field values, then storage simplicity is maintained, but client-specific data isolation cannot be achieved
Solution Approach 1:
The persistence unit is segmented into two separate persistence units: one for standard field values and another for extension field values. This segmentation enables client-specific data isolation while maintaining storage organization, directly resolving the contradiction between data isolation and storage simplicity.
2Adaptability or versatility
If multiple extension fields are created to store multiple values, then data storage capability is improved, but resource optimization cannot be achieved
Solution Approach 1:
A single extension field is designed to carry multiple values through a structured format, making it universal and multi-functional. This eliminates the need to create multiple separate extension fields for different values, achieving resource optimization while maintaining data storage capability.
3Productivity
If extension fields are stored together with standard fields, then retrieval process is simplified, but data access speed for client-specific data decreases
Solution Approach 1:
The retrieval process is segmented into two independent operations: retrieving standard field values from the standard persistence unit and retrieving extension field values from the extension persistence unit. This segmentation enables parallel processing and faster access to client-specific data, resolving the contradiction between access speed and process complexity.
Solution Approach 2:
Extension field values are extracted from the combined storage structure and placed in a separate persistence unit. This extraction allows the system to focus retrieval operations on specific data types, improving access speed for client-specific extension data while maintaining a simplified retrieval process through clear separation of concerns.
Data Source
AI summary
Various embodiments of systems and methods to provide multi-client generic persistence for extension nodes are described herein. A standard field value and an extension field value specific to a client of a business data object are separated. Further, an extension node instance key associated with the extension field value is segregated. Furthermore, the standard field value and associated standard node instance key are stored in a standard persistence unit, and the extension field value is stored in an extension data persistence unit. Also, the extension node instance key and a relation between the standard node instance key and the extension node instance key are stored in an extension key persistence unit.