Remote Service Request Mapping to Reduce Canonical Format Overhead
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IT solutions involving API calls between clients and servers spend significant CPU time mapping between internal formats and a common canonical format, increasing costs and decreasing performance, even when both sides use the same integration technology.
Innovation Solution
Implement a method where clients and servers exchange maps to optimize message formats, allowing one side to perform both mappings, thereby avoiding the use of a large canonical format and reducing CPU and network I/O costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a common canonical format is used for message exchange between client and server, then compatibility and interoperability are improved, but CPU time for format mapping increases and performance decreases
Solution Approach 1:
The client performs the format mapping operation in advance by translating its internal format to the server's format before sending the message. This preliminary action eliminates the need for the server to perform mapping, reducing overall CPU time and improving performance while maintaining compatibility.
Solution Approach 2:
The mapping operation is extracted from the server side and performed by the client side. By taking out the mapping burden from the server, the system achieves better performance while still using the canonical format for compatibility where needed.
2Adaptability or versatility
If complex format mapping is performed between internal formats and canonical format, then message compatibility is improved, but CPU load and network I/O costs increase
Solution Approach 1:
The client performs the complex format mapping operation in advance before message transmission. This preliminary action reduces the CPU load on the server and minimizes network I/O costs by sending the message in the final required format rather than requiring post-reception conversion.
Solution Approach 2:
Instead of the server converting incoming messages from canonical format to internal format (traditional approach), the client inverts the process by converting its internal format to the server's format before transmission. This inversion reduces server CPU load while maintaining compatibility.
3Ease of manufacture
If both client and server use the same integration technology, then ease of implementation is improved, but format mapping overhead still increases CPU time and costs
Solution Approach 1:
Even when both sides use the same integration technology, the client performs the mapping operation in advance. This preliminary action eliminates redundant mapping operations on the server side, reducing CPU time and costs while maintaining the ease of implementation provided by using the same technology stack.
Solution Approach 2:
The client performs the mapping operation even though the server could also perform it (excessive action on one side). This partial centralization of the mapping function on the client side eliminates duplicate mapping work and reduces overall CPU time consumption in the system.
Data Source
AI summary
A computer-implemented method, computer system, and computer program product for communication between a sender and a receiver according to a communication protocol, comprising: generating a message for sending to a receiver; translating the message from a sender format used by the sender into a predetermined format dependent on the communication protocol; sending the translated message to the receiver, the translated message comprising a map invitation; causing the receiver to translate the translated message into a receiver format used by the receiver; causing the receiver to exchange a first map indicative of a mapping between a first format and the predetermined format; and sending a subsequent message to the receiver in the first format.