Backend Controller Object for Frontend Service Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Frontend service adaptation leads to increased metadata processing, network data volume, memory consumption, and response time due to the need to evaluate multiple association paths and transfer data to the frontend server, negatively impacting performance.
Innovation Solution
Shifting service adaptation to the backend server by instantiating a controller object that maps nodes and attributes from business objects, reducing metadata on the frontend and minimizing roundtrips between servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If frontend service adaptation is implemented to combine fields from different business object nodes, then the user interface can display required business data, but metadata processing load and memory consumption on the frontend server increase significantly
Solution Approach 1:
The patent inverts the traditional service adaptation approach by moving the adaptation logic from the frontend server to the backend server. Instead of the frontend combining fields from multiple business objects, the backend controller object performs the adaptation and sends only the necessary adapted data to the frontend, thereby reducing frontend metadata processing load while maintaining UI display capabilities
Solution Approach 2:
The patent extracts the service adaptation functionality from the frontend server and relocates it to the backend controller layer. This extraction removes the complex metadata processing and association path evaluation from the frontend, leaving only the essential data display functionality
2Ease of operation
If all data on associated paths is transferred to the frontend server for runtime evaluation, then required business object fields can be accessed, but network data volume and response time deteriorate
Solution Approach 1:
The patent applies preliminary action by performing the service adaptation and data filtering at the backend before data transfer to the frontend. The controller object pre-evaluates association paths and prepares only the necessary adapted data, eliminating runtime evaluation delays on the frontend and reducing network data volume
Solution Approach 2:
The patent inverts the data transfer approach by having the backend send only adapted, filtered data to the frontend instead of transferring all raw data from association paths. This inversion reduces network data volume and eliminates the need for frontend runtime evaluation of multiple association paths
Data Source
Figure 1
Figure 2
Figure 3A~3B
AI summary
A request originating at a frontend server for data encapsulated in a plurality of business objects is received. The plurality of business objects are stored in a business object layer at the backend server remote from the frontend server. In addition, the request originates from a user interface layer is received at a controller layer. A controller object is instantiated in the controller layer at the backend server. Nodes of the controller object are mapped to nodes in the plurality of business objects so that the controller object encapsulates the request data. Thereafter, transmission of data response to the request encapsulated by the controller object to the frontend server is initiated. Related apparatus, systems, techniques and articles are also described.