Coexistence Layer API Conversion for Legacy Server Modernization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In conventional database management systems, the transformation of system of record components to new software platforms often results in incompatibility between caller logic from system of engagement devices and the target server, due to differences in API types, leading to inefficient communication and operational challenges.
Innovation Solution
A coexistence layer module utilizing robotic process automation (RPA) is introduced to intercept and convert caller logic from system of engagement requests to match the API type of the new target server, ensuring seamless communication and compatibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If system of record components are moved to a new software platform, then modernization and new capabilities are achieved, but API type incompatibility occurs between legacy server and new target server
Solution Approach 1:
A coexistence layer module is introduced as an intermediary component between the legacy server and the new target server. This module intercepts requests from the system of engagement, determines whether they point to moved system of record components, and converts the request signatures from the first API type to the second API type. The coexistence layer acts as a mediator that enables communication between incompatible systems without requiring changes to either the legacy server or the new target server.
2Reliability
If API type conversion is implemented manually, then compatibility is achieved, but transformation complexity and time increase
Solution Approach 1:
The coexistence layer module automatically performs API type conversion without requiring manual intervention. The module autonomously intercepts requests, references the mapping between API types, determines the appropriate conversion, and transforms the request signatures. This self-service approach eliminates the need for manual transformation processes and reduces the complexity associated with manual API conversion.
Solution Approach 2:
A mapping between API types is established in advance, documenting the relationships between the first API type recognized by the legacy server and the second API type recognized by the new target server. This preliminary action enables the coexistence layer module to quickly determine the appropriate conversion without performing complex analysis during request processing.
3Reliability
If all system of record operations remain on legacy server, then API compatibility is maintained, but modernization and platform migration are prevented
Solution Approach 1:
The system of record is segmented into components that can be independently moved to the new target server while other components remain on the legacy server. The coexistence layer module handles only the converted requests for moved components, allowing partial migration without requiring complete system relocation. This segmentation enables gradual modernization while maintaining compatibility for remaining legacy operations.
Data Source
AI summary
Updating calls or operations in a database management system includes mapping, by a computer processor, application programming interface (API) types associated with a legacy server and a new server. The legacy server recognizes request signatures of a first API type and the new server recognizes request signatures of a second API type that is distinct from the first API type. A request is received from a system of engagement, addressed to a system of records resident on a legacy server. The request is intercepted by a coexistence layer module. A determination is made of whether the intercepted request uses a request signature recognized by the first API type. The coexistence layer module converts the intercepted request to a format using the request signature of the second API type. The converted intercepted request is sent to the new server. The converted intercepted request is performed by the new server.