Traffic switching method and device, server, and storage medium

Abstract

The application provides a traffic switching method and device, a server and a storage medium. The method is applied to a unit architecture system, and the unit architecture system comprises a channel unit, a partition unit and a public unit. The method comprises the following steps: based on the channel unit, receiving traffic called from a distributed architecture system, and verifying traffic fallback function and traffic access function of the channel unit based on the called traffic; when the traffic fallback function and the traffic access function of the channel unit are both verified, calling service data from the public unit, and verifying traffic fallback function and data processing function of the partition unit based on the called service data and a service processing request sent by the channel unit; and when the traffic fallback function and the data processing function of the partition unit are both verified, switching all traffic in the distributed architecture system to the unit architecture system. The method provided by the application can solve the problem of how to improve the safety of traffic switching and the stability of system operation.

Description

Technical Field

[0001] This application relates to traffic switching technology between different data systems, and more particularly to a traffic switching method, apparatus, server, and storage medium. Background Technology

[0002] With the increasing volume of business requests and transaction data, banks tend to use distributed architecture systems to process business and store transaction data. However, distributed architecture systems have some uncorrectable drawbacks. For example, in terms of disaster recovery, distributed architecture systems experience a larger failure blast radius when facing regional failures and lack flexible emergency switching, and they cannot flexibly adapt to the deployment needs of geographically dispersed data centers. Regarding capacity, while server resources in a distributed architecture system can horizontally scale with the increase in user and business volume, the number of database connections and service provider connections will gradually approach their limits, leading to insufficient system capacity.

[0003] In light of the above shortcomings, a unitized architecture system has been developed to transform the original distributed architecture system. The unitized architecture system enables affinity deployment within a unit, significantly reducing unnecessary cross-unit access, effectively controlling the failure blast radius, improving switchover flexibility, and better adapting to the multi-site and multi-center deployment needs of future data centers. Furthermore, through unit partitioning and unit traffic management, it can ensure that the number of database connections and service provider connections does not approach their limits, thus supporting flexible horizontal capacity scaling. Based on this, current business processing requires switching traffic from the distributed architecture system to the unitized architecture system.

[0004] However, if an unexpected situation occurs during the flow switching process from the distributed architecture system to the unitized architecture system, preventing timely return flow, the flow switching may fail. Flow switching failure not only affects the operation of the unitized architecture system but also the normal operation of the original distributed architecture system. Therefore, how to develop a comprehensive flow switching plan to cope with various possible states, thereby improving the security of flow switching and the stability of system operation, remains a problem to be solved. Summary of the Invention

[0005] This application provides a traffic switching method, device, server, and storage medium to address the problem of how to formulate a complete traffic switching scheme to cope with various possible states, thereby improving the security of traffic switching and the stability of system operation.

[0006] On one hand, this application provides a traffic switching method applied to a unitized architecture system, the unitized architecture system including channel units, partition units, and common units; the method includes:

[0007] Based on the channel unit, traffic called from the distributed architecture system is received, and the traffic back-switching function and traffic access function of the channel unit are verified based on the called traffic.

[0008] When the traffic back-switching function and traffic access function of the channel unit are both verified, the business data is called from the public unit, and the traffic back-switching function and data processing function of the partition unit are verified based on the called business data and the business processing request sent by the channel unit.

[0009] When the traffic rollback function and data processing function of the partition unit are both verified, all traffic in the distributed architecture system is switched to the unitized architecture system.

[0010] In one embodiment, the channel unit includes a processing layer and multiple load balancing nodes; the traffic back-switching function and traffic access function of the channel unit based on call traffic verification include:

[0011] When the traffic being called does not support traffic switching, and it is determined that each load balancing node can switch the traffic being called back to the distributed architecture system, the traffic switching function of the channel unit is verified as successful.

[0012] When the traffic of the call supports flow switching, and it is determined that the access layer can successfully access any of the load balancing nodes that generate and send the service processing request based on the traffic of the call, the traffic access function of the channel unit is verified as successful.

[0013] In one embodiment, the traffic received by each load balancing node from the call is a preset proportion of the total traffic in the distributed architecture system;

[0014] The total traffic received by the multiple load balancing nodes is equal to the total traffic in the distributed architecture system.

[0015] In one embodiment, the common unit includes a first structured database, and the method further includes:

[0016] The system queries the first structured database to determine whether the traffic being called has a flow-cutting identifier.

[0017] When the traffic being called does not have a flow-switching identifier, it is determined that the traffic being called does not support flow-switching.

[0018] In one embodiment, when switching all traffic from the distributed architecture system to the unitized architecture system, the first structured database is used to store the business data corresponding to all traffic in the distributed architecture system.

[0019] In one embodiment, the partitioning unit includes a processing layer and a second structured database, and the called business data includes first business data that needs to be switched back and second business data that needs to be processed;

[0020] The verification of the traffic back-switching function and data processing function of the partition unit based on the business data of the call and the business processing request sent by the channel unit includes:

[0021] Based on the processing layer receiving the first service data, and upon confirming that the processing layer can switch the first service data back to the distributed architecture system, the traffic switching function of the partition unit is verified as successful.

[0022] When the processing layer receives the second service data and the service processing request, and processes the second service data after confirming that the processing layer can respond to the service processing request, and can send the processing result data to the second structured database for storage, the data processing function of the partition unit is confirmed to be verified as successful.

[0023] In one embodiment, the second structured database and the database in the distributed architecture system maintain real-time synchronization of the protocol.

[0024] In one embodiment, the distributed architecture system is equipped with an existing load balancing node, and the traffic in the distributed architecture system is switched to the unitized architecture system through the existing load balancing node.

[0025] In one embodiment, the unitized architecture system further includes monitoring nodes, statistics nodes, and alarm nodes, and the method further includes:

[0026] When an anomaly is detected in the access traffic of the channel unit based on the monitoring node, the first abnormal data of the access traffic of the channel unit is recorded based on the statistics node.

[0027] When an anomaly is detected in the business data corresponding to the traffic processed by the partition unit based on the monitoring node, the second anomaly data is recorded based on the statistics node when the business data corresponding to the traffic processed by the partition unit is processed.

[0028] When an anomaly is detected in the public unit storage service data by the monitoring node, the third anomaly data is recorded by the statistics node when the public unit storage service data is stored.

[0029] When the statistics node records the first abnormal data, or the second abnormal data, or the third abnormal data, an alarm is issued based on the alarm node.

[0030] On the other hand, this application provides a unitized architecture system, which includes channel units, partition units, and common units, and further includes:

[0031] The first verification module is used to receive traffic called from the distributed architecture system and verify the traffic back-off function and traffic access function of the channel unit based on the called traffic.

[0032] The second verification module is used to call business data from the public unit when the traffic back-switching function and traffic access function of the channel unit are both verified to be successful, and to verify the traffic back-switching function and data processing function of the partition unit based on the called business data and the business processing request sent by the channel unit.

[0033] The traffic switching module is used to switch all traffic in the distributed architecture system to the unitized architecture system when the traffic back-off function and data processing function of the partition unit are both verified.

[0034] On the other hand, this application provides a server, including: a processor, and a memory communicatively connected to the processor;

[0035] The memory stores computer-executed instructions;

[0036] The processor executes computer execution instructions stored in the memory to implement the traffic switching method as described in the first aspect.

[0037] On the other hand, this application provides a computer-readable storage medium storing computer-executable instructions that, when executed, cause a computer to perform the traffic switching method as described in the first aspect.

[0038] On the other hand, this application provides a computer program product, including a computer program that, when executed by a processor, implements the traffic switching method as described in the first aspect.

[0039] In summary, the traffic switching method provided in the embodiments of this application is applied to a unitized architecture system, which includes a channel unit, a partition unit, and a common unit. The channel unit is used to access traffic, the partition unit is used to process the business data corresponding to the traffic, and the common unit is used to store the business data. The traffic switching method includes: receiving traffic called from the distributed architecture system based on the channel unit, and verifying the traffic back-off function and traffic access function of the channel unit based on the called traffic; when the traffic back-off function and traffic access function of the channel unit are both verified, calling business data from the common unit, and verifying the traffic back-off function and data processing function of the partition unit based on the called business data and the business processing request sent by the channel unit; when the traffic back-off function and data processing function of the partition unit are both verified, switching all traffic in the distributed architecture system to the unitized architecture system.

[0040] In other words, before switching traffic, the backflow function and normal business processing capabilities of the unitized architecture system are verified in advance. The traffic switching process is only executed if the backflow function passes verification. In this way, if an unexpected situation occurs during the traffic switching process from the distributed architecture system to the unitized architecture system, the traffic can be switched back to the distributed architecture system in a timely manner, avoiding impact on the normal operation of the original distributed architecture system and improving the security of traffic switching and the stability of system operation. Attached Figure Description

[0041] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0042] Figure 1 A schematic diagram illustrating an application scenario of the traffic switching method provided in this application;

[0043] Figure 2 A flowchart illustrating a traffic switching method provided in one embodiment of this application;

[0044] Figure 3 A schematic diagram illustrating the interaction between a unitized architecture system and a distributed architecture system in a traffic switching method provided in one embodiment of this application;

[0045] Figure 4 A schematic diagram illustrating the interaction between a unitized architecture system and a distributed architecture system in a traffic switching method provided in another embodiment of this application;

[0046] Figure 5 A schematic diagram of a flow switching device provided in one embodiment of this application;

[0047] Figure 6 A schematic diagram of a server provided for one embodiment of this application.

[0048] The accompanying drawings have illustrated specific embodiments of this disclosure, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this disclosure to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0049] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0050] In the description of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0051] First, let's explain the terms used in this application:

[0052] Unit: A self-contained set that can meet the critical operations (including complete transaction processing) of important customer business. This set contains most of the critical services required for important customer business, as well as the data allocated to this unit.

[0053] Unitized architecture: The unit is used as the basic unit of deployment, and most of the key applications (or service groups) required for important customer-facing business are deployed within the unit.

[0054] VZone: A channel unit, a type of logical unit, is deployed in critical customer-facing business applications (or service groups) located at the channel entry point. This customer-facing business application or service group itself does not participate in business logic transaction processing; it only acts as the initiator of channel business instructions.

[0055] RZone: A partition unit is a type of logical unit, and multiple RZones can be deployed depending on the actual situation of the data center. RZone deployment is located downstream of the channel and is split according to the user dimension (or other characteristic dimensions unified in the business chain), or deployed in each unit as an equivalent critical application (or service group) for important customer-facing business. Data from different shards is processed by service nodes within different units.

[0056] GZone: A common unit, it is a type of logical unit deployed downstream in the channel. It is a non-critical customer-facing business application (or service group) that provides indivisible data and services, which may be depended upon by RZone or VZone.

[0057] Server Load Balancer (SLB) is a traffic distribution and control service that distributes access traffic to multiple backend cloud servers (ECS instances) according to forwarding policies, enabling multiple servers to provide the same business services. Load balancing expands the service capabilities of applications and enhances their availability.

[0058] With the increasing volume of business requests and transaction data, banks tend to use distributed architecture systems to process business and store transaction data. However, distributed architecture systems have some uncorrectable drawbacks. For example, in terms of disaster recovery, distributed architecture systems experience a larger failure blast radius when facing regional failures and lack flexible emergency switching, and they cannot flexibly adapt to the deployment needs of geographically dispersed data centers. Regarding capacity, while server resources in a distributed architecture system can horizontally scale with the increase in user and business volume, the number of database connections and service provider connections will gradually approach their limits, leading to insufficient system capacity.

[0059] To address the aforementioned shortcomings, a modular architecture system has been developed to transform the original distributed architecture system. The modular architecture system enables affinity deployment within units, significantly reducing unnecessary cross-unit access, effectively controlling the failure blast radius, improving switchover flexibility, and better adapting to the multi-site, multi-center deployment needs of future data centers. Furthermore, through unit partitioning and unit traffic management, it can ensure that the number of database connections and service provider connections does not approach their limits, thus supporting flexible horizontal capacity scaling. Based on this, current business processing requires switching traffic from the distributed architecture system to the modular architecture system. However, if an unforeseen situation occurs during the switchover process and timely return to the modular architecture system is not possible, the switchover may fail. This failure not only affects the operation of the modular architecture system but also the normal operation of the original distributed architecture system.

[0060] Based on this, this application provides a traffic switching method, apparatus, server, and storage medium. The traffic switching method is applied to a unitized architecture system, which includes channel units, partition units, and common units. The traffic switching method includes: receiving traffic invoked from a distributed architecture system based on the channel unit, and verifying the traffic back-off function and traffic access function of the channel unit based on the invoked traffic; when both the traffic back-off function and traffic access function of the channel unit are verified successfully, invoking business data from the common unit, and verifying the traffic back-off function and data processing function of the partition unit based on the invoked business data and the business processing request sent by the channel unit; when both the traffic back-off function and data processing function of the partition unit are verified successfully, switching all traffic from the distributed architecture system to the unitized architecture system.

[0061] In other words, before switching traffic, the backflow function and normal business processing capabilities of the unitized architecture system are verified in advance. The traffic switching process is only executed if the backflow function passes verification. In this way, if an unexpected situation occurs during the traffic switching process from the distributed architecture system to the unitized architecture system, the traffic can be switched back to the distributed architecture system in a timely manner, avoiding impact on the normal operation of the original distributed architecture system and improving the security of traffic switching and the stability of system operation.

[0062] The traffic switching method provided in this application is applied to electronic devices, such as servers equipped with a modular architecture system. Figure 1 This is a schematic diagram illustrating the application of the traffic switching method provided in this application, which is used in... Figure 1 The illustrated modular architecture system includes channel units (VZone), partition units (RZone), and common units (GZone). The channel unit is used to access traffic, the partition unit is used to process the business data corresponding to the traffic, and the common unit is used to store the business data. Figure 1 In this system, the electronic device receives traffic from the distributed architecture system via a channel unit (VZone) and verifies the traffic back-off and traffic access functions of the channel unit based on the invoked traffic. When both functions are verified, business data is invoked from the common unit, and the traffic back-off and data processing functions of the partition unit are verified based on the invoked business data and the business processing request sent by the channel unit. Once both functions are verified, all traffic from the distributed architecture system is switched to the unitized architecture system.

[0063] Please see Figure 2 One embodiment of this application provides a traffic switching method, applied to Figure 1The illustrated modular architecture system includes channel units, partition units, and common units. The channel unit is used to access traffic, the partition unit is used to process the business data corresponding to the traffic, and the common unit is used to store the business data.

[0064] The traffic switching method includes:

[0065] S210, based on this channel unit, receives traffic called from the distributed architecture system, and verifies the traffic back-off function and traffic access function of the channel unit based on the called traffic.

[0066] Please see Figure 3 The channel unit includes an access layer and multiple load balancer nodes (SLBs). Figure 3 (Only one load balancing node is shown as an example). This distributed architecture system is equipped with existing load balancing nodes (SLBs). Traffic in this distributed architecture system is switched to this unitized architecture system through this existing load balancing node. Specifically, this is achieved through methods such as... Figure 3 The network F5 load balancer shown proportionally and gradually switches traffic to the channel unit (VZone).

[0067] In one optional embodiment, the existing load balancing node in the distributed architecture system and the load balancing node of the channel unit are deployed first, and then a dedicated line traffic switching application is submitted to the network department. The network department platform clears the traffic on one dedicated line (this can be done by migrating the traffic to another dedicated line). Then, through network changes, a load balancing node is attached to the dedicated line with the cleared traffic, and the network department platform gradually switches the traffic back to the dedicated line. Specifically, a portion of the traffic is transferred to the channel unit's load balancing node using network F5 load balancing.

[0068] When calling traffic from a distributed architecture system, it can be determined whether the traffic supports traffic switching based on whether it carries a traffic switching identifier. When verifying the traffic back-off function and traffic access function of the channel unit based on the called traffic, the traffic back-off function of the channel unit is verified using traffic that does not support traffic switching, and the traffic access function of the channel unit is verified using traffic that supports traffic switching.

[0069] That is, when the traffic of the call does not support traffic switching, it verifies whether each load balancer node in the channel unit can switch the traffic of the call back to the distributed architecture system. When it is determined that each load balancer node can switch the traffic of the call back to the distributed architecture system, the traffic switching function of the channel unit is verified as successful.

[0070] When the traffic for the call supports traffic switching, verify whether each load balancer node in the channel unit can successfully access the traffic for the call. If it is determined that each load balancer node can successfully access the traffic for the call, and each load balancer node can generate a service processing request based on the traffic for the call, then it is determined that each load balancer node has successfully accessed the traffic. If it is determined that the access layer can successfully access the service processing request generated and sent by any of the load balancers based on the traffic for the call, then it is determined that the access layer has successfully accessed the traffic. The access layer then sends the service processing request to the partition unit.

[0071] When it is confirmed that each load balancer node can successfully access traffic, and the access layer can successfully access traffic, the traffic access function of the channel unit is considered to have passed verification. It should be noted that when verifying the traffic rollback function of the channel unit, the existing load balancer node and the load balancer node being verified must be kept in parallel.

[0072] In an optional embodiment, such as Figure 3 As shown, the public unit includes a first structured database (e.g., MySQL). When confirming whether the traffic of the call has a flow-switching identifier, the first structured database is used to query whether the traffic of the call has a flow-switching identifier. Specifically, the first structured database is queried through protocol fragmentation, and the flow-switching identifier obtained is used to confirm whether the traffic supports flow-switching.

[0073] In an optional embodiment, the traffic received by each load balancing node for the call represents a preset proportion of the total traffic in the distributed architecture system. This preset proportion can be set according to actual needs; for example, if the unitized architecture system includes four load balancing nodes, the preset proportion can be set to 25%. That is, the traffic rollback function of each load balancing node is verified using 25% of the traffic. In other words, the total traffic received by multiple load balancing nodes is equal to the total traffic in the distributed architecture system; for example, the total traffic received by the four load balancing nodes is equal to 100% of the traffic in the distributed architecture system.

[0074] S220: When the traffic back-off function and traffic access function of the channel unit are both verified, the business data is called from the common unit, and the traffic back-off function and data processing function of the partition unit are verified based on the called business data and the business processing request sent by the channel unit.

[0075] In an optional embodiment, the business data refers to the business data of a pre-selected subset of customers, such as bank employees. When verifying the traffic rollback capability of the partition unit based on this business data, the business data needs to include at least data capable of rollback, so that the traffic rollback capability of the partition unit can be verified based on this rollback-capable data. When verifying the data processing function of the partition unit, the business data needs to include at least data that does not require rollback but needs to be processed. Then, based on the business processing request received by the channel unit, the data that does not require rollback but needs to be processed is processed, and the data processing capability of the partition unit is verified based on the processing result.

[0076] In an optional embodiment, the partition unit includes a processing layer and a second structured database. The service data includes first service data requiring traffic rollback and second service data requiring processing. The first service data requiring rollback includes first service data without a traffic cutoff identifier and that cannot be processed; the second service data requiring processing refers to second service data with a traffic cutoff identifier and requiring a processing result. When verifying the traffic rollback function of the partition unit, the processing layer receives the first service data, and the system confirms that the processing layer can roll back the first service data to the distributed architecture system, thus confirming that the traffic rollback function of the partition unit has passed verification. When verifying the data processing function of the partition unit, the processing layer receives the second service data and the service processing request, and the system confirms that the processing layer can process the second service data after responding to the service processing request and can send the processing result data to the second structured database for storage, thus confirming that the data processing function of the partition unit has passed verification.

[0077] S230: When the traffic back-off function and data processing function of the partition unit are both verified, all traffic in the distributed architecture system is switched to the unitized architecture system.

[0078] When the traffic rollback function and traffic access capability of the channel unit are both verified and passed, and the traffic rollback capability and data processing function of the partition unit are both verified and passed, it proves that the unitized architecture system has the ability to roll back in a timely manner and can operate normally. Therefore, even if an unexpected situation occurs during the process of switching traffic from the distributed architecture system to the unitized architecture system, the traffic can be switched back to the distributed architecture system in a timely manner, and the switching will not fail due to the inability to switch back in a timely manner.

[0079] For example, when verifying the traffic rollback function of the channel unit, if the unitized architecture system fails, the network change can be implemented by switching back the switched traffic to the distributed architecture system through a one-click rollback pipeline.

[0080] Therefore, once the traffic rollback and traffic access capabilities of the channel unit have been verified, and the traffic rollback and data processing capabilities of the partition unit have also been verified, all traffic from the distributed architecture system will be switched to the unitized architecture system. When switching all traffic from the distributed architecture system to the unitized architecture system, a portion of the traffic from the distributed architecture system can be switched first, while some data is retained in the distributed architecture system for processing business needs. That is, the distributed architecture system and the unitized architecture system are kept in parallel for a period of time before the distributed architecture system is taken offline.

[0081] When all traffic in the distributed architecture system is switched to the unitized architecture system, the first structured database is used to store the business data corresponding to all traffic in the distributed architecture system.

[0082] In summary, the traffic switching method provided in this embodiment is applied to a unitized architecture system, which includes channel units, partition units, and common units. The channel unit is used to access traffic, the partition unit is used to process the business data corresponding to the traffic, and the common unit is used to store the business data. The traffic switching method includes: receiving traffic called from the distributed architecture system based on the channel unit, and verifying the traffic back-off function and traffic access function of the channel unit based on the called traffic; when the traffic back-off function and traffic access function of the channel unit are both verified, calling business data from the common unit, and verifying the traffic back-off function and data processing function of the partition unit based on the called business data and the business processing request sent by the channel unit; when the traffic back-off function and data processing function of the partition unit are both verified, switching all traffic in the distributed architecture system to the unitized architecture system.

[0083] In other words, before switching traffic, the backflow function and normal business processing capabilities of the unitized architecture system are verified in advance. The traffic switching process is only executed if the backflow function passes verification. In this way, if an unexpected situation occurs during the traffic switching process from the distributed architecture system to the unitized architecture system, the traffic can be switched back to the distributed architecture system in a timely manner, avoiding impact on the normal operation of the original distributed architecture system and improving the security of traffic switching and the stability of system operation.

[0084] Please see Figure 4 The distributed architecture system also includes a database (e.g., an Oracle database), and in an optional embodiment, the second structured database and the database in the distributed architecture system maintain real-time synchronization of protocols.

[0085] Specifically, when the protocol in the second structured database is updated, real-time synchronization is maintained with the database to ensure that the protocol in the database is also updated. For example, when a first protocol is added to the second structured database, the first protocol is also added to the database. Optionally, real-time synchronization of the protocol between the second structured database and the database is achieved through Kafka.

[0086] In addition, the database and the second structured database maintain end-of-day protocol synchronization. That is, the database uploads all protocols in the database once a day, and the second structured database updates its own protocols according to the uploaded protocols to maintain synchronization with the protocols in the database.

[0087] Please see Figure 4 In an optional embodiment, when switching traffic from the distributed architecture system to the unitized architecture system, existing protocols will be migrated between the database and the first structured database, as well as between the database and the second structured database. In addition, customer mapping information will be migrated between the database and the first structured database. This customer mapping information can be understood as customer information, including all customer information and information associated with the customer.

[0088] In the traffic switching method provided in the above embodiments, by maintaining the protocol synchronization between the distributed architecture system and the unitized architecture system, the protocol asynchrony problem caused by traffic switching is avoided, and the success rate of traffic switching is improved.

[0089] In an optional embodiment, the unitized architecture system further includes monitoring nodes, statistics nodes, and alarm nodes. During the process of traffic access to the unitized architecture system, the traffic switching method also records abnormal data and alarms. Specifically, when the monitoring node detects an anomaly when the channel unit accesses traffic, the statistics node records the first abnormal data of the channel unit accessing traffic. When the monitoring node detects an anomaly when the partition unit processes the business data corresponding to the traffic, the statistics node records the second abnormal data of the partition unit processing the business data corresponding to the traffic. When the monitoring node detects an anomaly when the common unit stores business data, the statistics node records the third abnormal data of the common unit storing business data. When the statistics node records the first, second, or third abnormal data, an alarm is triggered by the alarm node.

[0090] That is, when verifying the backflow capability and business processing capability of the modular architecture system, abnormal data and timely alarms should be recorded in a timely manner, so that staff can improve and enhance the backflow capability and business processing capability of the modular architecture system based on the abnormal data.

[0091] Please see Figure 5 An embodiment of this application also provides a unitized architecture system 10, which includes channel units, partition units, and common units, and further includes:

[0092] The first verification module 11 is used to receive traffic called from the distributed architecture system and verify the traffic back-off function and traffic access function of the channel unit based on the called traffic.

[0093] The second verification module 12 is used to call business data from the common unit when the traffic back-off function and traffic access function of the channel unit are both verified to be successful, and to verify the traffic back-off function and data processing function of the partition unit based on the called business data and the business processing request sent by the channel unit.

[0094] The traffic switching module 13 is used to switch all traffic in the distributed architecture system to the unitized architecture system when the traffic back-off function and data processing function of the partition unit are both verified.

[0095] The channel unit includes a processing layer and multiple load balancing nodes. The first verification module 11 is specifically used to: determine that the traffic back-switching function of the channel unit is verified as successful when the traffic of the call does not support traffic switching and it is determined that each load balancing node can switch the traffic of the call back to the distributed architecture system; and determine that the traffic access function of the channel unit is verified as successful when the traffic of the call supports traffic switching and it is determined that the access layer can successfully access the service processing request generated and sent by any load balancing node based on the traffic of the call. The traffic of the call received by each load balancing node is a preset proportion of the total traffic in the distributed architecture system; the total traffic received by multiple load balancing nodes is equal to the total traffic in the distributed architecture system.

[0096] The public unit includes a first structured database. The first verification module 11 is specifically used to query whether the traffic of the call has a flow-switching identifier through the first structured database. When the traffic of the call does not have a flow-switching identifier, it is determined that the traffic of the call does not support flow-switching. When all traffic in the distributed architecture system is switched to the unitized architecture system, the first structured database is used to store the business data corresponding to all traffic in the distributed architecture system.

[0097] The partition unit includes a processing layer and a second structured database. The business data invoked includes first business data that needs to be switched back and second business data that needs to be processed. The second verification module 12 is specifically used to: verify the traffic switching function of the partition unit when the processing layer receives the first business data and confirms that the processing layer can switch the first business data back to the distributed architecture system; and verify the data processing function of the partition unit when the processing layer receives the second business data and the business processing request and confirms that the processing layer can process the second business data after responding to the business processing request and can send the processing result data to the second structured database for storage.

[0098] The second structured database and the database in the distributed architecture system maintain real-time synchronization via a protocol.

[0099] The distributed architecture system is equipped with an existing load balancing node, through which traffic in the distributed architecture system is switched to the unitized architecture system.

[0100] The unitized architecture system also includes monitoring nodes, statistics nodes, and alarm nodes. The unitized architecture system 10 further includes a monitoring module 14. This monitoring module 14 is used to record, based on the statistics node, first abnormal data when an anomaly is detected in the traffic access of the channel unit, and second abnormal data when an anomaly is detected in the business data corresponding to the traffic processed by the partition unit, based on the statistics node. When an anomaly is detected in the storage of business data in the common unit, based on the monitoring node, third abnormal data is recorded in the statistics node. When the statistics node records the first, second, or third abnormal data, an alarm is issued based on the alarm node.

[0101] Please see Figure 6 One embodiment of this application also provides a server 20, including a processor 21 and a memory 22 communicatively connected to the processor 21. The memory 22 stores computer-executable instructions, and the processor 21 executes the computer-executable instructions stored in the memory 22 to implement the traffic switching method provided in any of the above embodiments.

[0102] This application also provides a computer-readable storage medium storing computer-executable instructions that, when executed, cause the computer-executable instructions to be executed by a processor to implement the traffic switching method provided in any of the preceding embodiments.

[0103] This application also provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the traffic switching method provided in any of the preceding embodiments.

[0104] It should be noted that the aforementioned computer-readable storage media can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc. It can also be various electronic devices that include one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0105] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0106] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0107] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0108] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0109] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0110] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0111] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A traffic switching method, characterized in that, The method is applied to a unitized architecture system, which includes channel units, partition units, and common units; the method includes: Based on the channel unit, traffic called from the distributed architecture system is received, and the traffic back-switching function and traffic access function of the channel unit are verified based on the called traffic. When the traffic back-switching function and traffic access function of the channel unit are both verified, the business data is called from the public unit, and the traffic back-switching function and data processing function of the partition unit are verified based on the called business data and the business processing request sent by the channel unit. When the traffic rollback function and data processing function of the partition unit are both verified, all traffic in the distributed architecture system is switched to the unitized architecture system. The channel unit includes an access layer and multiple load balancing nodes; the traffic back-switching function and traffic access function of the channel unit based on call traffic verification include: When the traffic being called does not support traffic switching, and it is determined that each load balancing node can switch the traffic being called back to the distributed architecture system, the traffic switching function of the channel unit is verified as successful. When the traffic of the call supports flow switching, and it is determined that the access layer can successfully access any of the load balancing nodes that generate and send the service processing request based on the traffic of the call, the traffic access function of the channel unit is verified as successful.

2. The method according to claim 1, characterized in that, The traffic received by each load balancing node is a preset proportion of the total traffic in the distributed architecture system. The total traffic received by the multiple load balancing nodes is equal to the total traffic in the distributed architecture system.

3. The method according to claim 1, characterized in that, The common unit includes a first structured database, and the method further includes: The system queries the first structured database to determine whether the traffic being called has a flow-cutting identifier. When the traffic being called does not have a flow-switching identifier, it is determined that the traffic being called does not support flow-switching.

4. The method according to claim 3, characterized in that, When switching all traffic from the distributed architecture system to the unitized architecture system, the first structured database is used to store the business data corresponding to all traffic in the distributed architecture system.

5. The method according to any one of claims 1 to 4, characterized in that, The partition unit includes a processing layer and a second structured database, and the business data to be called includes first business data that needs to be switched back and second business data that needs to be processed; The verification of the traffic back-switching function and data processing function of the partition unit based on the business data of the call and the business processing request sent by the channel unit includes: Based on the processing layer receiving the first service data, and upon confirming that the processing layer can switch the first service data back to the distributed architecture system, the traffic switching function of the partition unit is verified as successful. When the processing layer receives the second service data and the service processing request, and processes the second service data after confirming that the processing layer can respond to the service processing request, and can send the processing result data to the second structured database for storage, the data processing function of the partition unit is confirmed to be verified as successful.

6. The method according to claim 5, characterized in that, The second structured database and the database in the distributed architecture system maintain real-time synchronization of the protocol.

7. The method according to claim 1, characterized in that, The distributed architecture system is equipped with an existing load balancing node, and the traffic in the distributed architecture system is switched to the unitized architecture system through the existing load balancing node.

8. The method according to claim 1, characterized in that, The modular architecture system further includes monitoring nodes, statistics nodes, and alarm nodes, and the method further includes: When an anomaly is detected in the access traffic of the channel unit based on the monitoring node, the first abnormal data of the access traffic of the channel unit is recorded based on the statistics node. When an anomaly is detected in the business data corresponding to the traffic processed by the partition unit based on the monitoring node, the second anomaly data is recorded based on the statistics node when the business data corresponding to the traffic processed by the partition unit is processed. When an anomaly is detected in the public unit storage service data by the monitoring node, the third anomaly data is recorded by the statistics node when the public unit storage service data is stored. When the statistics node records the first abnormal data, or the second abnormal data, or the third abnormal data, an alarm is issued based on the alarm node.

9. A modular architecture system, characterized in that, The unitized architecture system includes channel units, partition units, and common units, and also includes: The first verification module is used to receive traffic called from the distributed architecture system and verify the traffic back-off function and traffic access function of the channel unit based on the called traffic. The second verification module is used to call business data from the public unit when the traffic back-switching function and traffic access function of the channel unit are both verified to be successful, and to verify the traffic back-switching function and data processing function of the partition unit based on the called business data and the business processing request sent by the channel unit. The traffic switching module is used to switch all traffic in the distributed architecture system to the unitized architecture system when the traffic back-off function and data processing function of the partition unit are both verified. The channel unit includes an access layer and multiple load balancing nodes; the traffic back-switching function and traffic access function of the channel unit based on call traffic verification include: When the traffic being called does not support traffic switching, and it is determined that each load balancing node can switch the traffic being called back to the distributed architecture system, the traffic switching function of the channel unit is verified as successful. When the traffic of the call supports flow switching, and it is determined that the access layer can successfully access any of the load balancing nodes that generate and send the service processing request based on the traffic of the call, the traffic access function of the channel unit is verified as successful.

10. A server, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the traffic switching method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when executed, cause the computer to perform the traffic switching method as described in any one of claims 1-8.

Images