Runtime UI Metadata-Driven Communication Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing frontend-backend communication systems consume significant resources and network bandwidth during business transactions, as they often require immediate processing and feedback, which is not necessary for all transactions, leading to inefficient use of memory, processing, and network resources.
Innovation Solution
A runtime UI application on a frontend server determines, based on business object metadata, whether processing by the backend business application is required for a user interface field input, triggering round-trip communication only when necessary to update fields before transaction completion, and suspending communication when not required.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If round-trip communication is triggered for every user input field in a business transaction, then data accuracy and completeness are improved, but network bandwidth consumption and system resource usage increase significantly
Solution Approach 1:
The system applies partial action by triggering round-trip communication only for specific field inputs that require backend processing, rather than for all inputs. The runtime UI application determines which fields need processing based on business object metadata, sending requests only when necessary to maintain data accuracy while reducing unnecessary network traffic.
Solution Approach 2:
Different fields are treated differently based on their processing requirements. The system assigns different communication behaviors to different field inputs - some fields trigger immediate round-trip communication while others are processed locally without backend interaction, optimizing resource usage based on local field characteristics.
2Loss of energy
If round-trip communication is suspended for fields not requiring immediate processing, then network bandwidth and system resources are conserved, but response time for updates may be delayed
Solution Approach 1:
The system applies partial action by suspending round-trip communication only for fields that do not require immediate backend processing. The runtime UI application identifies such fields using business object metadata and processes them locally, conserving system resources while maintaining timely updates for fields that truly require backend interaction.
Solution Approach 2:
The system performs preliminary action by pre-configuring business object metadata that identifies which fields require backend processing. This allows the runtime UI application to make immediate decisions about communication timing without delays, knowing in advance which fields need immediate updates and which can be processed later or locally.
3Loss of energy
If the runtime UI application uses business object metadata to determine processing requirements, then unnecessary communications are reduced, but the complexity of the UI application increases
Solution Approach 1:
The system introduces an intermediary element - the business object metadata - that mediates between the runtime UI application and the backend business application. The metadata contains pre-defined information about which fields require processing, allowing the UI application to make communication decisions without complex logic, effectively outsourcing the complexity to the metadata structure.
Solution Approach 2:
The business object metadata serves itself by containing all necessary information about field processing requirements. The runtime UI application simply reads and follows the metadata instructions without needing complex decision-making logic, allowing the metadata to effectively manage its own communication behavior autonomously.
Data Source
AI summary
The present description refers to a technique for providing a user interface from a runtime user interface (UI) application running on a frontend server to a client application, receiving, by the runtime UI application from a business application running on a backend server, a business object that includes metadata associated with the user interface, receiving, by the runtime UI application from the client application, user input associated with a business transaction, the user input including an input of a first field for the user interface, determining, by the runtime UI application based on the business object, whether processing by the business application of the first field input is required to determine and output to the client application an updated second field of the user interface before completion of the business transaction, and triggering a round-trip communication between the runtime UI application and the business application based on the determining.