Chained Service Calls with KeepBufferInSync Flag
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing service-oriented architecture for backend service layers results in inefficient processing of user interface requests due to multiple unnecessary service calls, leading to high network latency and increased support and development complexity, particularly when dealing with complex change services and redundant code execution.
Innovation Solution
The system introduces a 'KeepBufferInSync' flag that allows developers to chain backend service calls and suppress intermediate responses, reducing the number of roundtrips between the UI backend and the backend service layer by executing service calls in batches and condensing data updates, thereby optimizing network consumption and user interface performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If multiple service calls are executed separately in the backend service layer, then each service call can be processed independently, but the number of roundtrips increases and network latency accumulates
Solution Approach 1:
The patent combines multiple separate service calls into a single batched service call by introducing a chaining mechanism. Service calls that were previously executed separately with individual roundtrips are now merged into one consolidated request, reducing the number of network roundtrips and eliminating accumulated latency while maintaining independent processing capability through asynchronous execution within the batch.
2Reliability
If data is read and sent to UI client runtime after each service call, then data consistency is maintained, but the number of roundtrips and backend runtime consumption increases
Solution Approach 1:
The patent performs preliminary actions by executing all service calls in the batch first, then performing a single data read and synchronization operation after all service calls complete. This eliminates the need for intermediate data reads after each service call, reducing backend runtime consumption while maintaining data consistency through the batched approach and single synchronization point.
3Loss of time
If service calls are chained in batches, then network latency and roundtrips are reduced, but the complexity of modeling and executing chained operations increases
Solution Approach 1:
The patent introduces an intermediary batching mechanism that sits between the service consumer and the backend service layer. This intermediary captures multiple service calls, packages them into a batch, and manages the chaining execution, thereby reducing network latency while containing the complexity within the batching layer rather than propagating it throughout the entire system.
4Loss of energy
If intermediate responses are suppressed during batched service calls, then network consumption is reduced, but the ability to monitor individual service call progress is limited
Solution Approach 1:
The patent implements a feedback mechanism that provides progress information about batched service calls through alternative channels. Instead of sending intermediate responses over the network, the system provides feedback through local indicators, status updates, or asynchronous notifications, thereby reducing network consumption while maintaining visibility into service call progress through non-network feedback paths.
Data Source
AI summary
A computer-implemented system may include reception of a user interface request corresponding to two or more chained operations associated with one or more service calls to a backend service layer, determination of whether to update a backend buffer after execution of each of the one or more service calls, execution, if it is determined to update the backend buffer after execution of each of the one or more service calls, of each of the one or more service calls, and a read service call after execution of each of the one or more service calls, and execution, if it is determined not to update the backend buffer after execution of each of the one or more service calls, of each of the one or more service calls in sequence, and a bulk read service call only after execution of all of the one or more service calls.