Backend Service Adaptation for Data Retrieval Bottlenecks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data service adaptations between the provider layer and consumer layer, particularly in object-oriented computer programs, face performance issues due to the need for large metadata processing and transfer, which affects network data volume, memory consumption, and response times, especially when using normalized business objects for denormalized views in user interfaces and data analytics.
Innovation Solution
Implementing a back-end service adaptation system that receives query requests from consumer runtime environments, converts data using a language-specific data access service, and generates a target data object, reducing metadata on the frontend and optimizing performance by caching and validating execution plans through a compiler and interpreter, supporting various data formats and languages like BQL and SADL.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If frontend service adaptation is used to combine fields from different business object nodes, then a resulting adapted business object node can be used for displaying required business data in a user interface, but a large amount of metadata resides and is processed by a frontend server, negatively affecting performance, network data volume, memory consumption, and response time
Solution Approach 1:
The patent extracts the service adaptation functionality from the frontend server and relocates it to the backend system. The backend generates adapted business object nodes and sends only the necessary data to the frontend, removing the burden of metadata processing from the frontend server while maintaining the ability to provide customized views for different consumer needs
Solution Approach 2:
Instead of having the frontend combine fields from different business object nodes (frontend service adaptation), the patent inverts the approach by having the backend perform the field combination and generate adapted business object nodes (backend service adaptation). This reversal transfers the processing complexity from frontend to backend, improving frontend performance
2Adaptability or versatility
If all data on an associated path is transferred to the frontend server during runtime, then required business object fields can be accessed, but network data volume increases and response time deteriorates
Solution Approach 1:
The patent applies local quality by sending only the specific data needed for each consumer's requirements rather than all data on the associated path. The backend service adaptation mechanism determines exactly which fields and data are required and transfers only those, reducing network data volume and improving response time while maintaining data access flexibility
Solution Approach 2:
The patent performs service adaptation in advance during backend processing before data transfer to the frontend. By pre-combining fields and preparing adapted business object nodes before transmission, the system avoids runtime data gathering delays and reduces response time while maintaining the ability to access required business object fields
3Adaptability or versatility
If many association paths are evaluated on the frontend in order to access required business object fields, then data can be retrieved, but performance and response time are negatively affected
Solution Approach 1:
The patent extracts the association path evaluation and data retrieval operations from the frontend and relocates them to the backend. The backend service adaptation system evaluates association paths and retrieves data from business object nodes, then sends only the required results to the frontend, dramatically improving data access efficiency while maintaining retrieval capability
Solution Approach 2:
The patent introduces a backend service adaptation mechanism as an intermediary between the consumer's data requests and the business object nodes. This intermediary handles the complex association path evaluation and data retrieval operations, shielding the frontend from performance impacts while maintaining full data retrieval capability through standardized data transfer
Data Source
AI summary
A plurality of domain-specific service adaptation languages can be supported by a back-end service adaptation system to provide runtime access to a runtime instance of a data object comprising data stored in a repository. By defining a language-specific data access service and parser for each domain-specific service adaptation language, a single, service adaptation language-independent compiler and interpreter can prepare and execute a runtime load that includes an execution plan for retrieving and converting data from the repository for delivery in a data object according to a query request from a consumer runtime environment. A consumer using the consumer runtime environment can define the service adaptation language to be used and provide a parser and source code to enable access to business object data using the back-end service adaptation system.