API Server Reverse Proxy Configuration for Application Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Application migration from a cloud application platform to a container orchestration platform often results in application downtime and service interruptions due to environmental differences, with existing solutions being either costly or ineffective in maintaining continuous liveness and integrity of applications during the migration process.
Innovation Solution
A computer-implemented method that uses an API server to update a configuration map of a reverse proxy to route user service requests, build an image for applications, and generate pods on a worker node to migrate applications from a cloud platform to a container orchestration platform, ensuring continuous liveness and integrity without service interruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traffic routing proxies are used to maintain application connectivity during migration, then application liveness is maintained, but infrastructure cost and complexity increase significantly
Solution Approach 1:
The patent uses the service mesh's traffic routing proxy as an intermediary component that sits between the application and the external environment. The proxy maintains application connectivity by routing traffic to the appropriate application instances during migration, while the service mesh infrastructure manages the complexity of proxy configuration and coordination automatically.
Solution Approach 2:
The service mesh's traffic routing proxy serves multiple functions simultaneously: it maintains application connectivity, enables gradual migration through selective routing, provides traffic splitting capabilities, and manages service discovery. This multi-functionality eliminates the need for separate dedicated components for each migration task.
2Productivity
If all applications are migrated at once from cloud platform to container platform, then migration is completed quickly, but application downtime and service interruption occur
Solution Approach 1:
The patent segments the migration process into individual application-level operations rather than migrating all applications simultaneously. Each application can be migrated independently while others continue to run on the cloud platform, allowing continuous service delivery and eliminating large-scale downtime.
Solution Approach 2:
The service mesh enables dynamic traffic routing that can adapt in real-time during migration. Traffic can be dynamically switched between cloud-based applications and container-based applications as migration progresses, allowing the system to remain flexible and responsive throughout the migration process.
3Adaptability or versatility
If cloud application platform runtime is distributed to container orchestration platform, then virtual machine management is enabled, but container orchestration platform cannot recognize or manage customer applications on virtual machines
Solution Approach 1:
The service mesh acts as an intermediary layer between the container orchestration platform and applications running on virtual machines. It enables the container platform to manage and observe applications on VMs through standardized service interfaces without requiring direct integration or modification of the VM runtime environment.
Data Source
AI summary
Managing application migration is provided. An API server on a controller node is invoked to update a configuration map of a reverse proxy on a worker node for the reverse proxy to route user service requests corresponding to unmigrated applications of a set of applications from a first computing platform to a second computing platform to maintain liveness of the unmigrated applications during migration. The API server is invoked to build an image for an application of the set of applications based on source code of the application obtained from the second computing platform. The API server is invoked to generate a pod on the worker node to perform a workload of the application using the image. The API server is invoked to update a service on the worker node to select the pod on the worker node performing the workload of the application.