Translation Engine for Legacy Process Code Cloud Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Migrating legacy process code from on-premises or private cloud environments to public cloud environments is challenging due to differences in port mechanisms, dependencies, and database protocols, which can hinder the transition and require significant re-development of cloud-native process code.
Innovation Solution
A process code migration arrangement that includes an assembly worker and a migration tool with a translation engine and configuration manager, which generates configuration metadata and translates database protocol messages to ensure compatibility with the public cloud environment, allowing legacy process code to execute seamlessly with cloud-native applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If legacy process code is migrated directly to public cloud environment, then cloud-native application capabilities are improved, but compatibility issues arise due to differences in port mechanisms, dependencies, and database protocols
Solution Approach 1:
The patent introduces a translation engine as an intermediary component that sits between the legacy process code and the public cloud DBMS. This translation engine receives database protocol messages from the legacy code, translates them from the legacy database protocol to the cloud DBMS protocol, and forwards them to the cloud database. This mediator resolves the incompatibility between different database protocols while maintaining both legacy code functionality and cloud-native capabilities.
Solution Approach 2:
The patent segments the migration process into distinct functional components: a translation engine for protocol translation, a configuration manager for dependency management, and an assembly worker for code assembly. This segmentation allows each component to handle specific compatibility issues independently, making the overall migration process more manageable and reliable.
2Reliability
If legacy process code is re-created as cloud-native code, then compatibility with cloud environment is improved, but transition costs and development time increase significantly
Solution Approach 1:
The translation engine and configuration manager are set up in advance during the migration process, creating a ready-to-use translation layer before the legacy code needs to run in the cloud environment. This preliminary setup eliminates the need for time-consuming code rewriting, as the translation infrastructure is already in place to handle protocol conversions immediately upon deployment.
Solution Approach 2:
Instead of rewriting legacy process code as cloud-native code, the patent creates a translation layer that copies the functionality of the legacy database protocol into the cloud environment. The legacy code itself remains unchanged and is effectively copied over to the cloud, with the translation engine handling all necessary protocol adaptations, thus avoiding the time and cost of manual code recreation.
3Reliability
If translation engine is implemented to translate database protocol messages, then compatibility is maintained, but system complexity increases
Solution Approach 1:
The translation engine is designed as a universal component that can handle multiple database protocol translations through a configuration-driven approach. Rather than implementing separate translation mechanisms for each protocol pair, the translation engine uses a configuration manager to adapt to different legacy and cloud database protocols, making the system more complex in implementation but simpler in usage and maintenance.
Solution Approach 2:
The configuration manager automatically generates the necessary translation configurations and dependency mappings by analyzing the legacy process code and the target cloud environment. This self-service capability reduces manual configuration complexity, as the system automatically adapts the translation engine to the specific migration scenario without requiring extensive manual setup or complex configuration files.
Data Source
AI summary
Various examples are directed to systems and methods for operating a database management system (DBMS) in a cloud environment. An assembly worker executing at a first computing device may provide a first database protocol message generated by a process code executing at the first computing device. A translation engine executed at the cloud environment may translate the first database protocol message from a first format to a second format associated with a DBMS instance executing at the cloud environment to generate a translated first database protocol message. The translation engine may cause the translated first database protocol message to be provided to the DBMS instance and may receive, from the DBMS instance, a first reply corresponding to the translated first database protocol message. The first reply may be sent to the process code.