Backend Service Adaptation Layer for Denormalized Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data service adaptations between the provider and consumer layers in object-oriented computer programs are inefficient, leading to performance issues, increased network data volume, memory consumption, and response time due to the need for extensive metadata processing and multiple association path evaluations in frontend servers.
Innovation Solution
Implementing a service adaptation definition language (SADL) on a back-end system that creates denormalized data objects by retrieving and converting normalized data, reducing metadata on the frontend and minimizing roundtrips between frontend and backend systems, using a compiler and interpreter to generate and execute runtime loads for optimal performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If frontend service adaptation combines fields from different business object nodes to create adapted business object nodes, then data access flexibility for user interfaces is improved, but metadata volume and memory consumption on the frontend server increase significantly
Solution Approach 1:
The patent extracts the service adaptation logic and metadata processing from the frontend server and relocates it to the backend server. The backend server creates and manages adapted business object nodes, while the frontend server only consumes the adapted data without storing or processing the adaptation metadata. This extraction resolves the contradiction by maintaining data access flexibility through backend adaptation while eliminating frontend metadata volume accumulation.
Solution Approach 2:
The patent introduces a service adaptation layer as an intermediary between the normalized data sources and the frontend consumer. This adaptation layer, implemented on the backend, transforms normalized business objects into denormalized views with joined data from multiple association paths. The intermediary handles all metadata processing and adaptation logic, allowing the frontend to access flexible denormalized data without bearing the metadata overhead.
2Adaptability or versatility
If frontend service adaptation transfers all data on associated paths to the frontend server, then data access completeness is improved, but network data volume and processing overhead increase
Solution Approach 1:
The patent implements selective data transfer where the backend service adaptation logic identifies and transfers only the specific fields and data required by the frontend consumer, rather than transferring all data on entire association paths. The adaptation layer filters and prepares only the necessary denormalized data, reducing network data volume while maintaining data access completeness for the required fields.
3Adaptability or versatility
If multiple association paths are evaluated on the frontend to access required business object fields, then data access flexibility is improved, but response time and processing performance deteriorate
Solution Approach 1:
The patent performs service adaptation and data preparation in advance on the backend server before the frontend requests the data. The backend evaluates association paths, joins data from multiple business objects, and creates denormalized adapted business object nodes ahead of time. When the frontend requests data, the pre-adapted results are already available, eliminating runtime evaluation overhead and improving response time while maintaining flexible data access.
Data Source
AI summary
A back-end service adaptation system provides access to normalized data in a data repository for a consumer runtime environment sending a query request for denormalized data. The back-end service adaptation system can include a data access service layer, a parser layer, and a back-end service adaptation runtime layer. The consumer runtime can use a service adaptation definition language (SADL), and the parser and data access service can be configured to convert and translate the SADL request for the back-end service adaptation runtime layer.