Gateway migration method and system

Abstract

The application provides a gateway migration method and system, and relates to the field of computer systems. In the migration process, part of transaction traffic is degraded, and in specific cases, the service is retried without awareness. Through the method of coordinating the graceful start and stop of the machine, the gateway can be quickly migrated without affecting the service traffic. The application is compatible with multiple heterogeneous basic software and hardware platforms, and multiple degradation mechanisms ensure that the service traffic is lossless, which solves the afterthoughts of migration, avoids the influence of network restrictions, and at the same time, avoids the loss of service traffic, removes the awareness of the service unit, and parallelly processes two heterogeneous basic software and hardware platforms. The stable system is confirmed by comparison, the traffic is adjusted at any time, and the migration process is provided with progress and retreat.

Description

Technical Field

[0001] This invention relates to the field of computer systems, and more specifically, to a gateway migration method and system thereof. Background Technology

[0002] The financial services IT innovation migration plan utilizes ARM-based servers as computing nodes to support business applications, and plans to use a full-stack cloud platform that meets the requirements of IT innovation to manage these ARM computing nodes. Applications running on traditional x86 servers will be migrated to ARM servers based on the full-stack cloud platform. A smooth migration is required while maintaining RTO and RPO.

[0003] As the main carrier of east-west traffic in the financial sector, the service gateway handles hundreds of millions of calls per day. It needs to be migrated from one architecture to another, which can be described as "changing the engine of a flying plane".

[0004] Existing service gateway migration strategies generally fall into three categories: First, a shutdown migration, where services are suspended during the migration process. This method has a significant drawback: downtime is unacceptable in financial services. Second, a scaling-down migration, which involves first expanding the service gateway nodes on the new platform, then adjusting the upper-layer load balancer to switch some traffic to the expanded nodes, removing traffic from the historical platform. During periods of low or no traffic, the nodes on the historical platform are scaled down, and this process is repeated until all service traffic has migrated to the new platform. This method is complex, involves numerous intermediate states, and cannot roll back without impacting business traffic in case of problems. It also cannot guarantee no traffic loss during the switchover process. Third, a dual-gateway approach is used. A new gateway cluster is independently deployed on the new platform, compiled using adapted new gateway code. Newly deployed services connect to the new gateway. During the new gateway setup, a gateway bridge is built to bridge service calls between the two gateway clusters. As applications are gradually switched and updated, the historical gateway can be taken offline. This solution uses an application-adaptive gateway approach to achieve gateway migration, which does improve migration stability, but it also increases the migration cycle, increases the risk perceived by business users, and adds complexity to the gateway bridge.

[0005] ARM migration is divided into compiled language migration and interpreted language migration. During interpreted language migration, only the supporting services (such as Java's JVM) need to be adapted and migrated to the specified platform; the application can run with almost no recompilation. Compiled languages, due to their use of underlying hardware and software characteristics, employ assembly instructions in some aspects of the coding process. This requires adjustments to the target functions and recompilation for adaptation. Furthermore, the service gateway mentioned in this solution is written in Go, increasing the difficulty of migration and necessitating a reliable migration method for the system. Summary of the Invention

[0006] To address the needs outlined in the background section, this invention provides a gateway migration method and system. During the migration process, some transaction traffic is downgraded, and retrying is performed without affecting the business operations under specific circumstances. By combining this with a graceful start-up and shutdown method, the gateway can be migrated quickly without impacting business traffic.

[0007] A gateway migration method, comprising the following steps:

[0008] Step 1: Migrate and adapt Go language to heterogeneous underlying software and hardware platforms, ensuring feature compatibility and adapting assembly instructions;

[0009] Step 2: Develop a forward proxy with transparent penetration functionality and put it into production.

[0010] Step 3: Deploy the service gateway of the new platform and form a cluster with the x86 architecture service gateway. The clusters are synchronized via Gossip, and the routing table of the registry center is synchronized.

[0011] Step 4: Adjust the smart DNS, migrate some traffic to the ARM platform service gateway, verify the service gateway's operation, and track the correctness of business traffic.

[0012] Step 5: Remove X86 platform service gateway business traffic and disable new business traffic from entering; and notify the X86 platform service gateway to gracefully shut down and process in-transit transactions through the poison packet mechanism.

[0013] Step Six: Business applications that have established a long-term connection with the X86 platform service gateway should immediately switch links. In the above process, any degradation situations will be handled through multiple layers of degradation to ensure the stability of business traffic.

[0014] Step 7: Keep the X86 platform service gateway and the ARM platform service gateway coexisting for 1 week and observe their operation. If any unknown anomalies occur, immediately expand the X86 platform service gateway and shut down the ARM platform service gateway.

[0015] Step 8: One week later, expand the ARM platform service gateway and gracefully shut down the X86 platform service gateway to complete the entire service gateway migration process.

[0016] Furthermore: When a brief inability to make a call occurs during the migration process, or when there are network fluctuations, a multiple degradation mechanism will be triggered, prioritizing degradation to the forward proxy, which will then pass through the business traffic.

[0017] Furthermore: When the business system detects a call rejection at the service gateway, it downgrades its local routing table to select a route. The selected route is then passed through a forward proxy, which in turn passes the business traffic to the business unit, completing the RPC call.

[0018] Furthermore: If the forward proxy passthrough fails, the business system will directly select a route based on the routing information in the local routing table. The selected route will be accessed directly to the business unit via RPC call. If the business unit is also unreachable, the system will be downgraded to locating the internal service provided by the service content and accessing it directly through smart DNS.

[0019] Furthermore: a gateway migration system, comprising:

[0020] The compatibility module is used to ensure compatibility with various heterogeneous basic software and hardware platforms. It uses the same source code to achieve compatibility with the characteristics of heterogeneous basic software and hardware platforms and maintains a unified version.

[0021] The multi-level degradation module is used to ensure that business traffic is unaffected and avoid the impact of network restrictions. Business traffic is given priority to make RPC business calls through the service gateway cluster. When a brief call failure occurs during the migration process, or when network jitter occurs, the multi-level degradation mechanism will be triggered, and the traffic will be degraded to the forward proxy first.

[0022] The graceful start-stop module is used to avoid business traffic loss. Add the graceful start-stop module to the service gateway.

[0023] The intelligent DNS module is used to eliminate the need for business unit awareness;

[0024] The stability control module is used to compare and confirm system stability when two heterogeneous basic hardware and software platforms are used in parallel, and to adjust the flow rate as needed.

[0025] Furthermore, the terminal device may include a processor, a storage medium, and a bus. The storage medium stores machine-readable instructions that can be executed by the processor. When the terminal device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the deep learning model training method as described in the foregoing embodiments.

[0026] Further: a storage medium storing a computer program, which, when executed by a processor, performs the steps of the method described above.

[0027] Furthermore: a computer program product comprising a computer program that is executed by a processor using the methods described above.

[0028] The beneficial effects of this invention are: This invention is compatible with multiple heterogeneous basic software and hardware platforms, and multiple degradation mechanisms ensure that business traffic is not lost, which solves the worries of migration, avoids the impact of network restrictions, avoids business traffic loss, eliminates the awareness of business units, allows two heterogeneous basic software and hardware platforms to run in parallel, confirms system stability by comparison, and adjusts traffic at any time, providing a flexible approach to the migration process. Attached Figure Description

[0029] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 A flowchart of the method of the present invention is shown.

[0031] Figure 2 A schematic diagram of the system of the present invention is shown.

[0032] Figure 3 A schematic diagram of the composition of the terminal device of the present invention is shown. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in the present invention are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of the present invention. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this invention illustrate operations implemented according to some embodiments of the present invention. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this invention, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0034] Furthermore, the embodiments described herein are merely some, not all, of the embodiments of the invention. The components of the embodiments of the invention described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0035] It should be noted that the term "comprising" will be used in the embodiments of the present invention to indicate the presence of a feature subsequently declared, but does not preclude the addition of other features. It should also be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In the description of the present invention, it should also be noted that the terms "first," "second," "third," etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0036] The following is a detailed description of this case, in conjunction with the relevant accompanying drawings in the instruction manual.

[0037] like Figure 1 As shown, the present invention provides a gateway migration method, the specific steps of which include:

[0038] Step 1: Migrate and adapt Go language to heterogeneous underlying software and hardware platforms, ensuring feature compatibility and adapting assembly instructions.

[0039] Step 2: Develop a forward proxy with transparent penetration functionality and put it into production.

[0040] Step 3: Deploy the service gateway of the new platform and form a cluster with the x86 architecture service gateway. The clusters are synchronized via Gossip, and the routing table of the registry center is synchronized.

[0041] Step 4: Adjust the smart DNS, migrate some traffic to the ARM platform service gateway, verify the service gateway's operation, and track the correctness of business traffic.

[0042] Step 5: Remove X86 platform service gateway business traffic and disable new business traffic from entering; and notify the X86 platform service gateway to gracefully shut down and process in-transit transactions through the poison packet mechanism.

[0043] Step Six: Business applications that have established a long-term connection with the X86 platform service gateway should immediately switch links. In the above process, any degradation situations will be handled through multiple layers of degradation to ensure the stability of business traffic.

[0044] Step 7: Keep the X86 platform service gateway and the ARM platform service gateway coexisting for 1 week and observe their operation. If any unknown anomalies occur, immediately expand the X86 platform service gateway and shut down the ARM platform service gateway.

[0045] Step 8: One week later, expand the ARM platform service gateway and gracefully shut down the X86 platform service gateway to complete the entire service gateway migration process.

[0046] In this embodiment, the above method enables homogeneous evolution, ensuring compatibility with multiple heterogeneous underlying hardware and software platforms. It utilizes the same source code for heterogeneous underlying hardware and software platform feature compatibility, maintaining a unified version for convenient continuous evolution and maintenance. The compilation parameters are uniformly determined by the CI / CD platform; for example, if it's x86, it's packaged and compiled on an x86 machine with automated testing; if it's ARM, it's packaged and compiled on an ARM machine with automated testing. Because it's based on the same source and has consistent functionality, the same automated test cases can run on each platform, ensuring functional consistency and providing a foundation for a unified and smooth migration later on.

[0047] In another embodiment of this case, multiple degradation methods are used to ensure uninterrupted business traffic, resolving concerns about migration and mitigating the impact of network restrictions. Business traffic preferentially uses the service gateway cluster for RPC business calls. When a brief call failure occurs during the migration process, or when network fluctuations occur, a multiple degradation mechanism is triggered. First, it degrades to the forward proxy, which transmits business traffic transparently. If the business system detects a call rejection at the service gateway, it degrades its local routing table for route selection. The selected route is transmitted through the forward proxy, which then routes the business traffic to the business unit, completing the RPC call. If the forward proxy transmission fails, the business system directly selects a route based on the routing information in its local routing table. The selected route directly accesses the business unit via RPC. If the business unit is unreachable, it degrades to using internal service location based on the service content, directly accessing it through intelligent DNS, making every effort to ensure uninterrupted business migration.

[0048] Specifically, service 1 calls service 2, where service 2 has multiple service instances.

[0049] In the non-downgrade mode, the green line will be used, which will poll multiple instances of service 2 through the gateway for access.

[0050] After the first layer of degradation, it will follow the blue route and pass through the pass-through gateway. Service 1 will use local round-robin routing to select and call multiple instances of Service 2.

[0051] The second-level degradation then follows the dark green route, where Service 1 uses local round-robin routing to select and call multiple instances of Service 2.

[0052] The final third downgrade directly calls the preset service 2 instance node through resource location.

[0053] like Figure 2 As shown, the present invention provides a gateway migration system, comprising:

[0054] The compatibility module is designed to ensure compatibility with various heterogeneous underlying hardware and software platforms. It utilizes the same source code to achieve compatibility across these platforms, maintaining a unified version for easy continuous evolution and maintenance. The CI / CD platform determines compilation parameters: for x86 platforms, compilation and automated testing are performed on x86 machines; for ARM platforms, compilation and automated testing are performed on ARM machines. Because the functionality is consistent across platforms, the same automated test cases can run on each platform, ensuring functional consistency and providing a foundation for a unified and smooth migration process.

[0055] A multi-level degradation module ensures uninterrupted business traffic, alleviating concerns about migration and mitigating the impact of network restrictions. Business traffic prioritizes RPC calls through the service gateway cluster. During migration, if a brief call failure occurs or network fluctuations occur, a multi-level degradation mechanism is triggered. First, it degrades to the forward proxy, which transmits business traffic. If the business system detects a call rejection at the service gateway, it degrades its local routing table for routing selection. The selected route is transmitted through the forward proxy, which then routes the business traffic to the business unit, completing the RPC call. If the forward proxy fails to transmit the traffic, the business system directly selects a route based on the routing information in its local routing table. The selected route directly accesses the business unit via RPC. If the business unit is unavailable, it degrades to internal service location based on the service content, directly accessing it through intelligent DNS, making every effort to ensure a lossless business migration.

[0056] The graceful start / stop module is used to mitigate business traffic loss. Adding this module to the service gateway, along with a poisoned packet mechanism, maximizes the chances of completing transactions in transit.

[0057] The intelligent DNS module is used to eliminate the need for business units to be aware of the DNS. When accessing the service gateway within a business application, an internal unified resource location method is used. This allows for real-time adjustment of traffic routing, with short-connection access taking effect immediately and long-connection access being observed and activated during graceful shutdown.

[0058] The stability control module is used to compare and confirm system stability when two heterogeneous underlying hardware and software platforms operate in parallel. It adjusts traffic as needed, providing a flexible approach to the migration process. Because they originate from the same source, they operate in parallel for a period during the migration process to observe traffic stability and immediately switch back when abnormal traffic is detected, demonstrating good compatibility.

[0059] like Figure 3As shown, the terminal device 6 may include a processor 601, a storage medium 602, and a bus 603. The storage medium 602 stores machine-readable instructions executable by the processor 601. When the terminal device is running, the processor 601 communicates with the storage medium 602 via the bus 603. The processor 601 executes the machine-readable instructions to perform the steps of the deep learning model training method described in the foregoing embodiments. The specific implementation and technical effects are similar and will not be repeated here.

[0060] For ease of explanation, only one processor is described in the terminal device described above. However, it should be noted that in some embodiments, the terminal device of the present invention may also include multiple processors, and therefore the steps performed by one processor described in the present invention may also be performed jointly by multiple processors or individually.

[0061] The above are merely specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A gateway migration method, characterized by, The specific steps include: Step 1: Migrate and adapt Go language to heterogeneous underlying software and hardware platforms, ensuring feature compatibility and adapting assembly instructions; Step 2: Develop a forward agent with transparent pass-through function and put the forward agent into production; Step 3: Deploy the service gateway on the ARM platform and form a cluster with the X86 architecture service gateway. The clusters are synchronized via Gossip, and the routing table of the registry center is synchronized. Step 4: Adjust the smart DNS, migrate some traffic to the ARM platform service gateway, verify the service gateway's operation, and track the correctness of business traffic; Step 5: Remove X86 platform service gateway business traffic and disable new business traffic from entering; and notify the X86 platform service gateway to gracefully shut down and process in-transit transactions through the poison packet mechanism. Step Six: Business applications that have established a long connection with the X86 platform service gateway should immediately switch links. In the above process, any degradation situations will be handled through multiple layers of degradation to ensure the stability of business traffic. Step 7: Keep the X86 platform service gateway and the ARM platform service gateway coexisting for 1 week and observe the operation. If any unknown abnormalities occur, immediately expand the capacity of the X86 platform service gateway and disable the ARM platform service gateway. Step 8: One week later, expand the capacity of the ARM platform service gateway and perform a graceful shutdown on the X86 platform service gateway to complete the migration process of the entire service gateway. The method further includes: When a brief call failure occurs during the migration process, or when network jitter occurs, a multiple degradation mechanism will be triggered, prioritizing degradation to the forward proxy, which will then pass through the business traffic. When a business system detects a call rejection at the service gateway, it degrades to selecting a route based on the local routing table, transparently passing business traffic through a forward proxy, and reaching the business unit according to the selected route to complete the RPC call; If the forward proxy fails to pass through, the business system will directly select a route based on the routing information in the local routing table. The selected route will be accessed directly to the business unit via RPC call. If the business unit is also unreachable, the system will be downgraded to locating the internal service provided by the service content and accessing it directly through smart DNS.

2. A gateway migration system, characterized in that, To implement the method as described in claim 1, comprising: The compatibility module is used to ensure compatibility with various heterogeneous basic software and hardware platforms. It adapts to different heterogeneous basic software and hardware platforms based on the same source code in order to maintain a unified version. The multi-level degradation module is used to ensure that business traffic is unaffected and avoid the impact of network restrictions. Business traffic is given priority to make RPC business calls through the service gateway cluster. When a brief call failure occurs during the migration process, or when network jitter occurs, the multi-level degradation mechanism will be triggered, and the traffic will be degraded to the forward proxy first. The graceful start / stop module is used to avoid loss of business traffic; The intelligent DNS module is used to eliminate the need for business unit awareness; The stability control module is used to compare and confirm the stability of the operation when two heterogeneous basic hardware and software platforms are used in parallel, and to adjust the flow rate as needed.

3. A terminal device, characterized in that, include: The device includes a processor, a storage medium, and a bus. The storage medium stores machine-readable instructions executable by the processor. When the terminal device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the method as described in claim 1.

4. A storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, performs the steps of the method as described in claim 1.

5. A computer program product, comprising a computer program, characterized in that, The computer program, when executed by a processor, implements the method as described in claim 1.

Images