System stability judgment method and related equipment

Abstract

The embodiment of the invention discloses a system stability judgment method and related equipment, and relates to the technical field of computers. In the embodiment of the specification, the system at least comprises a sending end device deployed with a sending end proxy service and a receiving end device deployed with a receiving end proxy service. A sending end device obtains an initial request for indicating a receiving end device to provide a service, generates and sets an identifier for uniquely representing the initial request for the initial request through a sending end proxy service to obtain the request, and sends the request to the receiving end device. And the receiving end equipment receives the request, judges whether the identifier set in the request exists in the historical identifier library based on the receiving end proxy service, and determines that a preset abnormal condition does not occur in the system and quickly fails the request when determining that the identifier exists in the historical identifier library.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method for determining system stability and related equipment. Background Art

[0002] In systems with high stability requirements, such as consumer financial payment systems, it is necessary to ensure system reliability and availability, such as ensuring the continuity of transactions. In order to meet these requirements, a series of mechanisms and high availability architectures are usually adopted in system design to ensure that transactions can continue seamlessly even in the event of device failure or network fluctuations.

[0003] However, in daily use, the system will inevitably have stability issues. For example, the system may include devices such as servers that may go down, or network fluctuations due to device failure or other reasons. Server downtime may be caused by hardware failure, software crash, or system resource exhaustion. Network interruptions or fluctuations include data transmission delays, packet loss, network congestion, and other issues, which may result in lost transaction requests, delayed processing, or user payment failures.

[0004] The above abnormal conditions will affect the stability of the system. Therefore, how to determine whether an abnormal condition that affects the stability of the system has occurred in the system and determine the specific content of the abnormal condition is a problem that needs to be solved urgently. Summary of the invention

[0005] The embodiments of this specification provide a method and related devices for determining system stability, which can realize system stability determination without affecting the existing system architecture and improve the efficiency of system stability determination. The technical solution is as follows:

[0006] In a first aspect, an embodiment of this specification provides a method for determining system stability, wherein the system includes at least a sending end device and a receiving end device, and the method is applicable to a sending end device in which a sending end proxy service is deployed in the system, and the method includes:

[0007] Obtaining an initial request for instructing the receiving device to provide a service;

[0008] Generate and set an identifier uniquely representing the initial request for the initial request through the sender proxy service to obtain the request;

[0009] The request is sent to the receiving end device, so that when the receiving end device receives the request and determines that the identifier set in the request already exists in the historical identifier library, it is determined that no preset abnormal situation occurs in the system.

[0010] In a second aspect, an embodiment of this specification provides a method for determining system stability, wherein the system includes at least a sending end device and a receiving end device, and the method is applicable to a receiving end device in which a receiving end proxy service is deployed in the system, and the method includes:

[0011] Receiving a request from the transmitting end device; wherein the request is obtained based on the system stability determination method described in the first aspect;

[0012] By means of the receiving end proxy service, determining whether the identifier set in the request already exists in the historical identifier library;

[0013] When it is determined that the identifier already exists in the historical identifier library, it is determined that the preset abnormal situation does not occur in the system, and the request is quickly failed.

[0014] In a third aspect, an embodiment of the present specification provides a system stability judgment device, the system comprising at least a sending end device and a receiving end device, the device being suitable for being set on a sending end device in which a sending end proxy service is deployed in the system, the device comprising:

[0015] A request acquisition module, used to acquire an initial request for instructing the receiving end device to provide a service;

[0016] An identification generation module, used to generate and set an identification uniquely representing the initial request for the initial request through the sending end proxy service, so as to obtain a request;

[0017] A request sending module is used to send the request to the receiving device so that when the receiving device receives the request and determines that the identifier set in the request already exists in the historical identifier library, it is determined that no preset abnormal situation has occurred in the system, and the preset abnormal situation includes at least one of the following situations: physical device failure and network jitter in the system.

[0018] In a fourth aspect, an embodiment of the present specification provides a system stability judgment device, the system comprising at least a sending end device and a receiving end device, the device being applicable to be set on a sending end device in which a sending end proxy service is deployed in the system, the device comprising:

[0019] A request receiving module, used to receive a request from the sending end device; wherein the request is obtained based on the system stability determination method described in the first aspect;

[0020] An identification judgment module, used to judge whether the identification set in the request already exists in the historical identification library through the receiving end proxy service;

[0021] The abnormality judgment module is used to determine that the preset abnormal situation does not occur in the system when it is determined that the identifier already exists in the historical identifier library, and to quickly fail the request.

[0022] In a fifth aspect, an embodiment of the present specification provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0023] In a sixth aspect, an embodiment of the present specification provides a computer program product, wherein the computer program product stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0024] In a seventh aspect, an embodiment of the present specification provides an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0025] The beneficial effects brought by the technical solutions provided by some embodiments of this specification include at least:

[0026] In an embodiment of the present specification, the system at least includes a sending-end device deployed with a sending-end proxy service and a receiving-end device deployed with a receiving-end proxy service. The sending-end device obtains an initial request for indicating that the receiving-end device provides a service, generates and sets an identifier uniquely representing the initial request for the initial request through the sending-end proxy service to obtain a request, and sends the request to the receiving-end device. The receiving-end device receives the request, determines whether the identifier set in the request exists in a historical identifier library based on the receiving-end proxy service, and when it is determined that the identifier exists in the historical identifier library, determines that no preset abnormal situation occurs in the system and quickly fails the request.

[0027] In other words, the preset abnormal situation refers to the situation where the transaction request of the sending device cannot reach the receiving device. Before the receiving device responds to the request of the sending device and provides services, it can determine through the receiving agent service that the unique identifier set in the request that represents the request already exists in the historical identifier library, and determine that the request has been successfully received, thereby determining that there is no abnormal situation in the system that causes the request to fail to reach the receiving device.

[0028] The embodiments of this specification deploy proxy services on the sending device and the receiving device respectively, and use the system stability judgment method to accurately identify whether there are abnormal conditions that affect the system stability, such as physical device failure or network jitter, in the system without affecting the system architecture, so as to solve the abnormal conditions in time and improve the system stability. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0030] Figure 1 It is a schematic diagram of the architecture of a method for determining system stability provided in an embodiment of this specification;

[0031] Figure 2 It is a flowchart of a method for determining system stability provided by an embodiment of this specification;

[0032] Figure 3 This is a schematic diagram of a scenario in which a sending end device sends a request provided in an embodiment of this specification;

[0033] Figure 4 It is a flowchart of a method for determining system stability provided by an embodiment of this specification;

[0034] Figure 5 This is a schematic diagram of a scenario in which a receiving end device receives a request provided in an embodiment of this specification;

[0035] Figure 6 It is a flowchart of a method for determining system stability provided by an embodiment of this specification;

[0036] Figure 7 It is a scenario diagram of a method for determining system stability provided by an embodiment of this specification;

[0037] Figure 8 It is a scenario diagram of a method for determining system stability provided by an embodiment of this specification;

[0038] Fig. 9 It is a structural schematic diagram of a system stability judgment device provided in an embodiment of this specification;

[0039] Fig.10 It is a structural schematic diagram of a system stability judgment device provided in an embodiment of this specification;

[0040] Fig.11 It is a structural schematic diagram of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0042] In the description of this specification, it should be understood that the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In the description of this specification, it should be noted that, unless otherwise clearly specified and limited, "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. For those of ordinary skill in the art, the specific meanings of the above terms in this specification can be understood in specific circumstances. In addition, in the description of this specification, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are an "or" relationship.

[0043] The present specification is described in detail below with reference to specific embodiments.

[0044] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in the embodiments of this specification are all authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions. For example, the features, information and data involved in this specification are all obtained with full authorization.

[0045] In systems with high stability requirements, such as consumer financial payment systems, it is necessary to ensure system reliability and availability, such as ensuring the continuity of transactions. In order to meet these requirements, a series of mechanisms and high availability architectures are usually adopted in system design to ensure that transactions can continue seamlessly even in the event of device failure or network fluctuations.

[0046] However, in daily use, the system will inevitably have stability issues. For example, the system may have downtime, network fluctuations due to equipment failure or other reasons. Server downtime may be caused by hardware failure, software crash or system resource exhaustion. Network interruptions or fluctuations include data transmission delays, packet loss, network congestion and other problems, which may result in transaction request loss, delayed processing or user payment failure. The above abnormal situations will affect the stability of the system.

[0047] Therefore, how to determine whether an abnormal situation that affects system stability has occurred in the system and determine the specific content of the abnormal situation is an issue that needs to be solved urgently.

[0048] like Figure 1 As shown, Figure 1 It is a schematic diagram of the architecture of a method for determining system stability provided in an embodiment of this specification. Figure 1 The system shown includes at least a plurality of transmitting end devices and a receiving end device 101, and the plurality of transmitting end devices include at least a transmitting end device 1021, a transmitting end device 1022 and a transmitting end device 1023. It can be understood that Figure 1 The number of servers and electronic devices shown in the figure is for illustration only, and this specification does not impose any limitation on this.

[0049] In the embodiments of this specification, the sending device refers to a device that sends a request to the receiving device 101, and the receiving device 101 refers to a device that responds to the request to provide a service to the sending device. In other words, the sending device can be understood as a client device, and the receiving device 101 refers to a server device.

[0050] The above-mentioned receiving device 101 can be a server. For example, the receiving device 101 is a plurality of physical servers, and the plurality of physical servers are independent in hardware. Or, the receiving device 101 is a plurality of virtual servers, and the plurality of virtual servers are deployed in the same hardware resource pool, and the deployment methods of the virtual servers include but are not limited to: VMware, Virtual Box and Virtual PC. It is understandable that the receiving device 101 also has other service capabilities and functions to complete the tasks in the following embodiments. For example, the receiving device 101 also provides portal services, resource management services, and CI / CD services, etc.

[0051] The transmitting devices such as transmitting device 1021, transmitting device 1022 and transmitting device 1023 include but are not limited to physical or virtual processors, mobile stations (Mobile Station, MS), mobile terminal equipment (Mobile Terminal), mobile phones (Mobile Telephone), handsets and portable equipment (portable equipment), Bluetooth headsets, smart watches and other types. The electronic devices can communicate with one or more core networks via a radio access network (Radio Access Network, RAN).

[0052] The sending end device 1021, the sending end device 1022, and the sending end device 1023 may also be equipped with a display device, which may be any device capable of realizing a display function, for example, the display device may be a cathode ray tube display (CR), a light-emitting diode display (LED), an electronic ink screen, a liquid crystal display (LCD), a plasma display panel (PDP), etc. For example, a user may use the display device on the sending end device 1021 to instruct the sending end device 1021 to receive an initial request.

[0053] The sending device and the receiving device 101 can communicate through a communication link established by a communication protocol, such as the gRPC protocol. gRPC is a high-performance, general-purpose open source remote procedure call (RPC) framework, which is mainly designed for mobile application development and based on the HTTP / 2 protocol standard, based on the protocol buffer (PB) serialization protocol development, and supports many development languages. In addition, the communication link can also be a wireless communication link or a wired communication link, for example, a wired communication link includes an optical fiber, a twisted pair or a coaxial cable, and a wireless communication link includes a Bluetooth communication link, a wireless fidelity (WIreless-FIdelity, Wi-Fi) communication link or a microwave communication link, etc.

[0054] based on Figure 1 The architecture shown, Figure 2The figure is a flow chart of a method for judging system stability provided by an embodiment of the present specification. The method can be implemented by a computer program, is applicable to a sending-end device in which a sending-end proxy service is deployed in the system, and can be run on a system stability judgment device based on the von Neumann system. The computer program can be integrated into an application or run as an independent tool application.

[0055] Specifically, the system stability judgment method includes:

[0056] S102: Obtain an initial request for instructing the receiving device to provide a service.

[0057] The sending end device obtains an initial request based on a preset trigger condition, and the initial request is used to instruct the receiving end device to provide a specific service. The specific form, content and requested service type of the initial request may vary according to different application scenarios and protocols.

[0058] The method for the sending end device to obtain the initial request may be that the user sends it to the sending end device, for example, the user inputs a URL through the Web application displayed on the display device of the sending end device to initiate an HTTP request. The method for the sending end device to obtain the initial request may also be that the device automatically detects, for example, when the sending end device is started, it broadcasts, requests network services, or sends a "detection request" to discover the receiving end device to link the receiving end device so as to use the services provided by the receiving end device. In the embodiments of this specification, other possible methods for obtaining the initial request are also included.

[0059] The form and content of the initial request may vary according to different protocols and application scenarios. For example, the initial request is in the form of an HTTP request, the context of which includes the requested URL (indicating the requested resource or service), request headers (e.g., user agent, content type, etc.), request body (for POST and PUT requests, it may carry data such as user input, authentication information, etc.), query parameters (used to pass additional parameters, usually in the form of key-value pairs), etc.

[0060] S104. Generate and set an identifier that uniquely represents the initial request for the initial request through the sending end proxy service to obtain the request.

[0061] A sender agent service is deployed on the sender device. In the embodiments of this specification, the sender agent service (Client Agent) can be deployed on the sender device in two ways. One deployment method is a local agent service, which is deployed on each sender device as part of the application of the sender device and communicates with the receiving device through the middle layer. Another deployment method is an external agent service, which processes requests by configuring an external agent (such as an API gateway, a reverse proxy).

[0062] like Figure 3 As shown, Figure 3 This is a schematic diagram of a scenario in which a sending end device sends a request provided by an embodiment of this specification. Through a local proxy service, a sending end proxy service 201 Client agent is deployed in the sending end device.

[0063] The sender proxy service generates an identifier that uniquely represents the initial request for the initial request. This identifier is used as the unique key of the request, which is a field or a group of fields used to uniquely mark each request in the database. Similar to the primary key, the unique key must also be unique, but can contain null values, and there can be multiple unique keys in the database. It is used to prevent duplicate data from being inserted into the database and ensure that only requests marked with the identifier exist in the database.

[0064] The method for generating the identifier may be to use a UUID (Universally Unique Identifier), such as 5e5d8b89-2. The method for generating the identifier may also be to combine the current timestamp with a random number to generate a unique identifier, such as 20241121-15674. The method for generating the identifier may also be to generate a unique identifier by hashing certain features of the initial request (such as request content, URL, user ID, etc.).

[0065] Based on the unique identifier generated to represent the initial request, the sender proxy service sets the identifier for the initial request to obtain the request. The sender proxy service attaches the identifier to the context of the request so that the request can be tracked and managed throughout the request lifecycle. For example, this can be accomplished through a context transfer mechanism, such as a tracing system such as OpenTelemetry or Zipkin, which sets the identifier to the context of the request across services to achieve full-link tracing.

[0066] In one embodiment, the sender proxy service uses bytecode technology to generate and dynamically set an identifier that uniquely represents the initial request for the initial request. Bytecode technology can be understood as a technology that dynamically modifies or enhances the function of a program while it is running. By operating the bytecode of the initial request, an identifier that serves as a monitoring point can be added without changing the source code.

[0067] like Figure 3As shown, the sending end proxy service 201 generates 2021 and dynamically sets an identifier 203 that uniquely represents the initial request for the initial request through the bytecode technology Java assist, and obtains the request 2022. For example, it is necessary to generate a unique identifier for the HTTP initial request, and pass the identifier as a request header in the context of the request. Through the bytecode technology JavaAssist, logic can be dynamically inserted when the sending end device executes the method for processing the request, a UUID can be generated as an identifier, and the identifier can be set as the HTTP header of the request.

[0068] In one embodiment, an identifier uniquely representing an initial request is generated by an identifier generation technology through a sending-end proxy service, and the identifier is dynamically set to the initial request using bytecode technology to obtain a request; wherein the identifier generation technology at least includes: a Snowflake algorithm. The Snowflake algorithm is a distributed unique identifier generation algorithm. The generated identifier is 64 bits long and can contain information such as a timestamp, a machine ID, a data center ID, and a serial number to ensure global uniqueness. The Snowflake algorithm has the characteristics of quickly generating identifiers, and the generated incremental identifiers are conducive to database index optimization and support for distributed deployment.

[0069] like Figure 3 As shown, the sending end proxy service 201 generates an identifier 203 that uniquely represents the initial request 2021 through an identifier generation technology such as the Snow flake algorithm, and uses the bytecode technology Java assist to dynamically set the identifier 203 to the initial request 2021 to obtain the request 2022. In other embodiments, the identifier generation technology may also include Nano ID, timestamp plus random number (Timestamp+Random), etc.

[0070] In this embodiment, the bytecode technology can be used to seamlessly embed the identifier into the initial request to obtain the request without modifying the source code of the initial request, thereby reducing the impact on the existing system architecture and the cost of modification, and improving the flexibility and scalability of the solution.

[0071] S106: Send a request to the receiving device.

[0072] The sending device sends a request with a flag set to the receiving device through the sending interface of the sending device, so that the receiving device receives the request and determines whether an abnormal situation occurs in the system. Figure 3 As shown, the sending end device sends the request 2022 with the identifier 203 set to the receiving end device 205Server.

[0073] In one embodiment, the preset abnormal situation includes at least one of the following situations: a physical device failure in the system, a network jitter. In other words, the preset abnormal situation refers to a situation where a transaction request of a sending end device cannot reach a receiving end device.

[0074] The receiving device receives the request and determines whether the identifier set in the request already exists in the historical identifier library.

[0075] When the identifier already exists in the historical identifier library, it indicates that the receiving device has received the request in the historical time period and stored the identifier carried in the request in the historical identifier library. Therefore, it can be determined that there is no preset abnormal situation in the system that causes the transaction request to fail to reach the receiving device. At this time, other sending devices may have repeatedly sent requests in the system. For example, if there is network jitter in the test system, or the receiving device does not respond to the request of the sending device in time, the above situations will cause the sending device to repeatedly send the same request to the receiving device.

[0076] When the identifier does not exist in the historical identifier library, it indicates that the receiving device has not received the request in the historical time period, so it can be determined that a preset abnormal situation occurs in the system that causes the transaction request to fail to reach the receiving device.

[0077] In one embodiment, the system further includes a first routing device and a second routing device. The sending end device sends a request to the receiving end device through the first routing device; when the service provided by the receiving end device in response to the request is not received, the sending end device sends a request to the receiving end device through the second routing device, so that the receiving end device receives the request multiple times and determines whether the identifier set in the request already exists in the historical identifier library, so as to determine whether a preset abnormal situation occurs in the system, and the preset abnormal situation includes network jitter caused by the first routing device.

[0078] Router is a network device used to forward data between different devices based on different networks. It determines the target path for transmitting transaction data from the sending device to the receiving device based on the target IP address of the transaction data (such as the request in this specification). Routers usually connect multiple networks, which can be the connection between a local area network (LAN) and a wide area network (WAN), or the connection between different local area networks.

[0079] In the embodiment of the present specification, the system includes at least two routing devices, a sending device and a receiving device. The sending device sends a request to the receiving device through the first routing device, and when the receiving device does not provide a service in response to the request, the sending device continues to send a request to the receiving device through the second routing device, considering that the first routing device may have a physical device failure or network jitter and other problems, and can also continue to send requests to the receiving device through other routing devices until the service is obtained when the receiving device does not provide a service in response to the request.

[0080] The receiving device receives the request multiple times, and determines whether the identifier set in the request already exists in the historical identifier library to determine whether a preset abnormal situation occurs in the system, and the preset abnormal intelligence includes network jitter caused by the first routing device. For example, the receiving device determines that a preset abnormal situation such as a failure of the first routing device or network jitter occurs when the sending device sends the request through the first routing device based on the second routing device receiving the request and determining that the identifier set in the request already exists in the historical identifier library.

[0081] In an embodiment of the present specification, the system at least includes a sending-end device deployed with a sending-end proxy service and a receiving-end device deployed with a receiving-end proxy service. The sending-end device obtains an initial request for indicating that the receiving-end device provides a service, generates and sets an identifier uniquely representing the initial request for the initial request through the sending-end proxy service to obtain a request, and sends the request to the receiving-end device. The receiving-end device receives the request, determines whether the identifier set in the request exists in a historical identifier library based on the receiving-end proxy service, and when it is determined that the identifier exists in the historical identifier library, determines that no preset abnormal situation occurs in the system and quickly fails the request.

[0082] In other words, the preset abnormal situation refers to the situation where the transaction request of the sending device cannot reach the receiving device. Before the receiving device responds to the request of the sending device and provides services, it can determine through the receiving agent service that the unique identifier set in the request that represents the request already exists in the historical identifier library, and determine that the request has been successfully received, thereby determining that there is no abnormal situation in the system that causes the request to fail to reach the receiving device.

[0083] The embodiments of this specification deploy proxy services on the sending device and the receiving device respectively, and use the system stability judgment method to accurately identify whether there are abnormal conditions that affect the system stability, such as physical device failure or network jitter, in the system without affecting the system architecture, so as to solve the abnormal conditions in time and improve the system stability.

[0084] In one embodiment, Figure 4As shown, it is a flow chart of a method for judging system stability provided by an embodiment of this specification. The method can be implemented by a computer program, is applicable to a receiving device in which a receiving agent service is deployed in the system, and can be run on a system stability judgment device based on a von Neumann system. The computer program can be integrated into an application or run as an independent tool application.

[0085] Specifically, the system stability judgment method includes:

[0086] S202: Receive a request from a sending device.

[0087] The request is made by the receiving device based on Figure 2 - Figure 3 The system stability determination method shown is obtained. The receiving device receives the request from the sending device through the network connection between the receiving device and the sending device.

[0088] like Figure 5 As shown, Figure 5 A schematic diagram of a scenario in which a receiving end device receives a request provided in an embodiment of this specification: The receiving end device receives a request 303 sent from a sending end device 302 Client.

[0089] S204: Determine, through the receiving end proxy service, whether the identifier set in the request already exists in the historical identifier library.

[0090] A client agent service is deployed on the receiving device. In the embodiments of this specification, the client agent service can be deployed on the receiving device in two ways. One deployment method is a local agent service, which is deployed on each receiving device as part of the application of the receiving device and communicates with the receiving device through the middle layer. Another deployment method is an external agent service, which processes requests by configuring an external agent (such as an API gateway, a reverse proxy). Figure 5 As shown, a receiving-end proxy service 301 Sever agent is deployed in a receiving-end device through a local proxy service.

[0091] The historical identification library can be understood as a memory dedicated to storing identifications set in requests received within a historical time period. In the historical identification library, identifications are related to the receiving time so that identifications within the historical time period can be traced, queried, and analyzed. The types of historical identification libraries can be classified according to storage media, data models, and functional requirements, and the embodiments of this specification do not impose any restrictions on this.

[0092] like Figure 5As shown, the receiving end agent service 301 receives the request 303, and determines whether the identifier 3031 set in the request 303 already exists in the historical identifier library 304 Storage. The method for querying whether the identifier 3031 exists in the historical identifier library 304 can be based on SQL statement query, etc.

[0093] In other words, before the receiving-end proxy service 301 responds to the request 303 and provides the corresponding service to the sending-end device 302, it determines whether the identifier 3031 set in the request 303 already exists through the identifiers received in multiple historical time periods stored in the historical identifier library 304. Since the identifier uniquely represents the request, it can determine whether the request 303 has been received within the historical time period.

[0094] S206: When it is determined that the identifier already exists in the historical identifier library, it is determined that no preset abnormal situation or fast failure request occurs in the system.

[0095] When the identifier already exists in the historical identifier library, it indicates that the receiving device has received the request within the historical time period and stored the identifier carried in the request in the historical identifier library. Therefore, it can be determined that there is no preset abnormal situation in the system that causes the transaction request to fail to reach the receiving device, and the request fails quickly.

[0096] like Figure 5 As shown, the receiving end proxy service 301 determines that the identifier 3031 exists in the historical identifier library 304, and quickly fails the request based on the Failover principle or other methods. In a distributed system, Failover is an important fault-tolerant mechanism that aims to improve the availability and reliability of the system. When the receiving end proxy service 301 determines that the identifier 3031 exists in the historical identifier library 304 and determines that no preset abnormal situation occurs in the system, the request 303 is failed based on the Failover principle.

[0097] In one embodiment, when it is determined that the identifier does not exist in the historical identifier library, the identifier is stored in the historical identifier library, and a service is provided to the sending end device in response to the request. When it is determined that the identifier does not exist in the historical identifier library, the identifier is associated with a timestamp and stored in the historical identifier library. The timestamp can be the current time or the time when the request is received. Further, the corresponding service is provided to the sending end device based on the specific content of the request. Figure 5 As shown, when the receiving-end proxy service 301 determines that the identifier does not exist in the historical identifier library 304, it instructs the receiving-end device to provide services to the sending-end device.

[0098] In one embodiment, the receiving-end proxy service determines whether the identifier already exists in the historical identifier library based on a storage engine with strict timing transaction control. When using the receiving-end proxy service to determine whether the identifier already exists in the historical identifier library based on a storage engine with strict timing transaction control, the receiving-end device proxy service needs to ensure the transactional and timing consistency of the operation, especially for transactions such as identifier storage, query, and request response in a high-concurrency environment, all of which need to be operated strictly in accordance with the timing.

[0099] The storage engine provides strict sequential transaction control to ensure that the state changes of the identifier can be changed in a timely manner. Typical storage engines include database engines that support distributed transactions, ACID (atomicity, consistency, isolation, persistence) features, and timestamp sorting.

[0100] In this embodiment, by combining the receiving-end proxy service with a storage engine with strict timing transaction control, effective management of identifiers can be achieved, ensuring that transactions such as identifier query, storing identifiers in a historical identifier library, or failed requests are performed based on strict timing.

[0101] In one embodiment, the system also includes: a first routing device and a second routing device; receiving a request from a sending device, including: receiving a request sent from the sending device through the second routing device; after determining whether the identifier set in the request already exists in the historical identifier library, it also includes: when it is determined that the identifier does not exist in the historical identifier library, determining that a preset abnormal situation occurs in the system, and providing a service to the sending device in response to the request, the preset abnormal situation includes network jitter caused by the first routing device.

[0102] Router is a network device used to forward data between different devices based on different networks. It determines the target path for transmitting transaction data from the sending device to the receiving device based on the target IP address of the transaction data (such as the request in this specification). Routers usually connect multiple networks, which can be the connection between a local area network (LAN) and a wide area network (WAN), or the connection between different local area networks.

[0103] In the embodiment of the present specification, the system includes at least two routing devices, a sending device and a receiving device. The sending device sends a request to the receiving device through the first routing device, and when the receiving device does not provide a service in response to the request, the sending device continues to send a request to the receiving device through the second routing device, considering that the first routing device may have a physical device failure or network jitter and other problems, and can also continue to send requests to the receiving device through other routing devices until the service is obtained when the receiving device does not provide a service in response to the request.

[0104] The receiving device receives the request multiple times, and determines whether the identifier set in the request already exists in the historical identifier library to determine whether a preset abnormal situation occurs in the system, and the preset abnormal intelligence includes network jitter caused by the first routing device. For example, the receiving device determines that a preset abnormal situation such as a failure of the first routing device or network jitter occurs when the sending device sends the request through the first routing device based on the second routing device receiving the request and determining that the identifier set in the request already exists in the historical identifier library.

[0105] In an embodiment of the present specification, the system at least includes a sending-end device deployed with a sending-end proxy service and a receiving-end device deployed with a receiving-end proxy service. The sending-end device obtains an initial request for indicating that the receiving-end device provides a service, generates and sets an identifier uniquely representing the initial request for the initial request through the sending-end proxy service to obtain the request, and sends the request to the receiving-end device. The receiving-end device receives the request, determines whether the identifier set in the request exists in a historical identifier library based on the receiving-end proxy service, and when it is determined that the identifier exists in the historical identifier library, determines that no preset abnormal situation occurs in the system and quickly fails the request. By deploying proxy services on the sending-end device and the receiving-end device respectively, and by using a system stability judgment method, the embodiment of the present specification can accurately identify whether an abnormal situation that affects the stability of the system, such as a physical device failure or network jitter, occurs in the system without affecting the architecture of the system, thereby promptly resolving the abnormal situation and improving the stability of the system.

[0106] In one embodiment, Figure 6 As shown, it is a flow chart of a method for judging system stability provided by an embodiment of this specification. The method can be implemented by a computer program, is applicable to a receiving device in which a receiving-end proxy service is deployed and a sending-end device in which a sending-end proxy service is deployed in the system, and can be run on a system stability judgment device based on a von Neumann system. The computer program can be integrated into an application or run as an independent tool application.

[0107] Specifically, the system stability judgment method includes:

[0108] S302: The sending end device obtains an initial request for instructing the receiving end device to provide a service.

[0109] Refer to the above S102, which will not be repeated here.

[0110] S304: The sending end device generates and sets an identifier that uniquely represents the initial request for the initial request through the sending end proxy service, thereby obtaining the request.

[0111] Refer to the above S104, which will not be repeated here.

[0112] S306: The sending device sends a request to the receiving device.

[0113] Refer to the above S106, which will not be repeated here.

[0114] S308: The receiving device receives the request from the sending device.

[0115] Refer to the above S202, which will not be repeated here.

[0116] S310: The receiving device determines, through the receiving agent service, whether the identifier set in the request already exists in the historical identifier library.

[0117] Refer to the above S204, which will not be repeated here.

[0118] S312: When the receiving device determines that the identifier already exists in the historical identifier library, it determines that no preset abnormal situation or fast failure request occurs in the system.

[0119] Refer to the above S206, which will not be repeated here.

[0120] S314: When the receiving device determines that the identifier does not exist in the historical identifier database, it stores the identifier in the historical identifier database and provides services to the sending device in response to the request.

[0121] In one embodiment, Figure 7 As shown, Figure 7 This is a scenario diagram of a method for determining system stability provided by an embodiment of this specification. The sender proxy service 401 in the sender device sends a request 403 with an identifier set to the receiving device through the first routing device 404 for the first time. Due to a preset abnormal situation of network jitter in the system, the request sent by the sender device for the first time is not received by the receiving device. The sender device does not receive the service provided by the receiving device, and the sender proxy service 401 sends the request 403 to the receiving device through the second routing device 405 for the second time.

[0122] The receiving device proxy service 402 receives the request 403 through the second routing device 405, and determines that the identifier set in the request 403 does not exist in the historical identifier library 406. Therefore, it is determined that a preset abnormal situation of network jitter occurs in the system, resulting in the request sent by the sending device for the first time not being received by the receiving device.

[0123] Figure 7The scenario of the system stability judgment method shown is also applicable to the network anti-shake scenario of the test system. Based on the requirements of the network anti-shake test, the sender proxy service 401 of the sender device sends the same request with a unique identifier to the receiving device multiple times. The receiving device receives the request multiple times and determines whether the identifier set in the request exists in the historical identifier library, thereby testing the network anti-shake performance of the system.

[0124] In one embodiment, Figure 8 As shown, Figure 8 This is a scenario diagram of a method for determining system stability provided by an embodiment of this specification. The sender proxy service 501 in the sender device sends a request 503 with an identifier set to the receiver device through the first routing device 504 for the first time. Due to an abnormal response timeout in the system, the request sent by the sender device for the first time was not responded to in time after being received by the receiver device. The sender device did not receive the service provided by the receiver device, and the sender proxy service 501 sent a request 503 to the receiver device through the second routing device 505 for the second time.

[0125] The receiving device proxy service 502 receives the request 503 for the first time through the first routing device 504 and stores the identifier in the request 503 in the historical identifier library 506. The receiving device proxy service 502 receives the request 503 through the second routing device 505, and determines that the identifier set in the request 503 already exists in the historical identifier library 406. Therefore, it is determined that an abnormal situation such as a response timeout has occurred in the system, and in this abnormal situation, the receiving device will repeatedly receive the same request.

[0126] In an embodiment of the present specification, the system at least includes a sending-end device deployed with a sending-end proxy service and a receiving-end device deployed with a receiving-end proxy service. The sending-end device obtains an initial request for indicating that the receiving-end device provides a service, generates and sets an identifier uniquely representing the initial request for the initial request through the sending-end proxy service to obtain the request, and sends the request to the receiving-end device. The receiving-end device receives the request, determines whether the identifier set in the request exists in a historical identifier library based on the receiving-end proxy service, and when it is determined that the identifier exists in the historical identifier library, determines that no preset abnormal situation occurs in the system and quickly fails the request. By deploying proxy services on the sending-end device and the receiving-end device respectively, and by using a system stability judgment method, the embodiment of the present specification can accurately identify whether an abnormal situation that affects the stability of the system, such as a physical device failure or network jitter, occurs in the system without affecting the architecture of the system, thereby promptly resolving the abnormal situation and improving the stability of the system.

[0127] The following are device embodiments of this specification, which can be used to implement the method embodiments of this specification. For details not disclosed in the device embodiments of this specification, please refer to the method embodiments of this specification.

[0128] See also Fig. 9 , which shows a schematic diagram of the structure of a system stability judgment device provided by an exemplary embodiment of this specification. The system includes at least a sending end device and a receiving end device, and the device is suitable for being set on a sending end device in which a sending end proxy service is deployed in the system. The system stability judgment device can be implemented as all or part of the device through software, hardware or a combination of both. The device includes a request acquisition module 601, an identification generation module 602 and a request sending module 603.

[0129] A request acquisition module 601 is used to acquire an initial request for instructing the receiving end device to provide a service;

[0130] The identification generation module 602 is used to generate and set an identification that uniquely represents the initial request for the initial request through the sending end proxy service to obtain the request;

[0131] The request sending module 603 is used to send the request to the receiving end device, so that when the receiving end device receives the request and determines that the identifier set in the request already exists in the historical identifier library, it determines that no preset abnormal situation occurs in the system.

[0132] In one embodiment, the identification generation module 602 includes:

[0133] The identifier generation unit is used to generate and dynamically set an identifier that uniquely represents the initial request for the initial request by using bytecode technology through the sending end proxy service.

[0134] In one embodiment, the identification generating unit includes:

[0135] The identifier generation subunit generates an identifier that uniquely represents the initial request by using the identifier generation technology through the sending-end proxy service, and dynamically sets the identifier to the initial request by using bytecode technology to obtain the request; wherein the identifier generation technology at least includes: a snowflake algorithm.

[0136] In one embodiment, the system further comprises: a first routing device and a second routing device;

[0137] The request sending module 603 includes:

[0138] A first sending module, configured to send the request to the receiving end device through the first routing device;

[0139] The system stability judging device further comprises:

[0140] A second sending module is used to send the request to the receiving device through the second routing device when the service provided by the receiving device in response to the request is not received, so that the receiving device receives the request multiple times and determines whether the identifier set in the request already exists in the historical identifier library, so as to determine whether the preset abnormal situation occurs in the system, and the preset abnormal situation includes a failure of the first routing device or network jitter.

[0141] In one embodiment, the preset abnormal situation includes at least one of the following situations: a physical device failure in the system and a network jitter.

[0142] See also Fig.10 , which shows a schematic diagram of the structure of a system stability judgment device provided by an exemplary embodiment of this specification. The system includes at least a sending end device and a receiving end device, and the device is suitable for being set on a sending end device in which a sending end proxy service is deployed in the system. The system stability judgment device can be implemented as all or part of the device through software, hardware or a combination of both. The device includes a request receiving module 701, an identification judgment module 702 and an abnormality judgment module 703.

[0143] The request receiving module 701 is used to receive a request from the sending end device; wherein the request is based on Figure 2 - Figure 3 The system stability judgment method shown is obtained;

[0144] The identification judgment module 702 is used to judge whether the identification set in the request already exists in the historical identification library through the receiving end proxy service;

[0145] The abnormality judgment module 703 is used to determine that the preset abnormal situation does not occur in the system and quickly fail the request when it is determined that the identifier already exists in the historical identifier library.

[0146] In one embodiment, the system stability determination device further includes:

[0147] The identification storage module is used to store the identification in the historical identification library when it is determined that the identification does not exist in the historical identification library, and to provide the service to the sending end device in response to the request.

[0148] In one embodiment, the identification determination module 702 includes:

[0149] The identification judgment unit is used to judge whether the identification already exists in the historical identification library based on the storage engine with strict timing transaction control through the receiving end proxy service.

[0150] In one embodiment, the system further comprises: a first routing device and a second routing device;

[0151] The request receiving module 701 includes:

[0152] an identification receiving unit, configured to receive a request sent from the sending end device via the second routing device;

[0153] The system stability judging device further comprises:

[0154] An abnormality judgment unit is used to determine that the preset abnormal situation occurs in the system when it is determined that the identifier does not exist in the historical identifier library, and to provide the service to the sending end device in response to the request. The preset abnormal situation includes a failure of the first routing device or network jitter.

[0155] In an embodiment of the present specification, the system at least includes a sending-end device deployed with a sending-end proxy service and a receiving-end device deployed with a receiving-end proxy service. The sending-end device obtains an initial request for indicating that the receiving-end device provides a service, generates and sets an identifier uniquely representing the initial request for the initial request through the sending-end proxy service to obtain the request, and sends the request to the receiving-end device. The receiving-end device receives the request, determines whether the identifier set in the request exists in a historical identifier library based on the receiving-end proxy service, and when it is determined that the identifier exists in the historical identifier library, determines that no preset abnormal situation occurs in the system and quickly fails the request. By deploying proxy services on the sending-end device and the receiving-end device respectively, and by using a system stability judgment method, the embodiment of the present specification can accurately identify whether an abnormal situation that affects the stability of the system, such as a physical device failure or network jitter, occurs in the system without affecting the architecture of the system, thereby promptly resolving the abnormal situation and improving the stability of the system.

[0156] It should be noted that the system stability judgment device provided in the above embodiment only uses the division of the above functional modules as an example when executing the system stability judgment method. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the system stability judgment device provided in the above embodiment and the system stability judgment method embodiment belong to the same concept, and the implementation process thereof is detailed in the method embodiment, which will not be repeated here.

[0157] The serial numbers of the embodiments of this specification are for description only and do not represent the advantages or disadvantages of the embodiments.

[0158] The present specification also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 1 - Figure 8 The system stability determination method of the embodiment shown in the figure can be specifically implemented by referring to Figure 1 - Figure 8 The specific description of the illustrated embodiment will not be repeated here.

[0159] The present specification also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor as described above. Figure 1 - Figure 8 The system stability determination method of the embodiment shown in the figure can be specifically implemented by referring to Figure 1 - Figure 8 The specific description of the illustrated embodiment will not be repeated here.

[0160] See also Fig.11 , is a schematic diagram of the structure of an electronic device provided in the embodiment of this specification. Fig.11 As shown, the electronic device 800 may include: at least one processor 801 , at least one network interface 804 , a user interface 803 , a memory 805 , and at least one communication bus 802 .

[0161] The communication bus 802 is used to realize the connection and communication between these components.

[0162] The user interface 803 may include a display screen (Display) and a camera (Camera), and the optional user interface 803 may also include a standard wired interface and a wireless interface.

[0163] The network interface 804 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0164] Among them, the processor 801 may include one or more processing cores. The processor 801 uses various interfaces and lines to connect various parts within the entire server 800, and executes various functions and processes data of the server 800 by running or executing instructions, programs, code sets or instruction sets stored in the memory 805, and calling data stored in the memory 805. Optionally, the processor 801 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 801 can integrate one or more combinations of a processor (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 801, and it can be implemented separately through a chip.

[0165] Among them, the memory 805 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 805 includes a non-transitory computer-readable storage medium. The memory 805 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 805 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 805 may also be optionally at least one storage device located away from the aforementioned processor 801. As Fig.11 As shown, the memory 805 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a system stability determination application.

[0166] exist Fig.11In the electronic device 800 shown, the user interface 803 is mainly used to provide an input interface for the user and obtain data input by the user; and the processor 801 can be used to call the system stability judgment application stored in the memory 805, and specifically perform the following operations:

[0167] Obtaining an initial request for instructing the receiving device to provide a service;

[0168] Generate and set an identifier uniquely representing the initial request for the initial request through the sender proxy service to obtain the request;

[0169] The request is sent to the receiving end device, so that when the receiving end device receives the request and determines that the identifier set in the request already exists in the historical identifier library, it is determined that no preset abnormal situation occurs in the system.

[0170] In one embodiment, the processor 801 executes the proxy service of the sender, generates and sets an identifier uniquely representing the initial request for the initial request, and obtains the request, specifically performing:

[0171] Through the sending end proxy service, bytecode technology is used to generate and dynamically set an identifier that uniquely represents the initial request for the initial request.

[0172] In one embodiment, the processor 801 executes, through the sender proxy service, using bytecode technology to generate and dynamically set an identifier that uniquely represents the initial request for the initial request, specifically performing:

[0173] The request is obtained by using the identifier generation technology to generate an identifier that uniquely represents the initial request through the sending-end proxy service, and using bytecode technology to dynamically set the identifier to the initial request; wherein the identifier generation technology includes at least: a snowflake algorithm.

[0174] In one embodiment, the system further comprises: a first routing device and a second routing device;

[0175] The processor 801 executes the sending of the request to the receiving end device, specifically performing:

[0176] Sending the request to the receiving device through the first routing device;

[0177] After executing the step of sending the request to the receiving device through the first routing device, the processor 801 further executes:

[0178] When the service provided by the receiving device in response to the request is not received, the request is sent to the receiving device through the second routing device, so that the receiving device receives the request multiple times and determines whether the identifier set in the request already exists in the historical identifier library, so as to determine whether the preset abnormal situation occurs in the system, and the preset abnormal information includes the failure of the first routing device or network jitter.

[0179] In one embodiment, the preset abnormal situation includes at least one of the following situations: a physical device failure in the system and a network jitter.

[0180] In one embodiment, the processor 801 may be used to call the system stability determination application stored in the memory 805, and specifically perform the following operations:

[0181] Receive a request from the sending device; wherein the request is based on Figure 2 - Figure 4 The system stability judgment method shown is obtained;

[0182] By means of the receiving end proxy service, determining whether the identifier set in the request already exists in the historical identifier library;

[0183] When it is determined that the identifier already exists in the historical identifier library, it is determined that the preset abnormal situation does not occur in the system, and the request is quickly failed.

[0184] In one embodiment, after executing the receiving end proxy service to determine whether the identifier set in the request already exists in the historical identifier library, the processor 801 further executes:

[0185] When it is determined that the identifier does not exist in the historical identifier library, the identifier is stored in the historical identifier library, and the service is provided to the sending end device in response to the request.

[0186] In one embodiment, the processor 801 performs the process of determining, through the receiving end proxy service, whether the identifier set in the request already exists in the historical identifier library by:

[0187] Through the receiving end proxy service, based on the storage engine with strict timing transaction control, it is determined whether the identifier already exists in the historical identifier library.

[0188] In one embodiment, the system further comprises: a first routing device and a second routing device;

[0189] The processor 801 executes the receiving of the request from the sending end device, specifically executing:

[0190] receiving a request sent from the sending device through the second routing device;

[0191] After the processor 801 executes the step of determining whether the identifier set in the request already exists in the historical identifier library, the processor 801 further executes:

[0192] When it is determined that the identifier does not exist in the historical identifier library, it is determined that the preset abnormal situation occurs in the system, and the service is provided to the sending end device in response to the request. The preset abnormal situation includes a failure of the first routing device or a network jitter.

[0193] In an embodiment of the present specification, the system at least includes a sending-end device deployed with a sending-end proxy service and a receiving-end device deployed with a receiving-end proxy service. The sending-end device obtains an initial request for indicating that the receiving-end device provides a service, generates and sets an identifier uniquely representing the initial request for the initial request through the sending-end proxy service to obtain the request, and sends the request to the receiving-end device. The receiving-end device receives the request, determines whether the identifier set in the request exists in a historical identifier library based on the receiving-end proxy service, and when it is determined that the identifier exists in the historical identifier library, determines that no preset abnormal situation occurs in the system and quickly fails the request. By deploying proxy services on the sending-end device and the receiving-end device respectively, and by using a system stability judgment method, the embodiment of the present specification can accurately identify whether an abnormal situation that affects the stability of the system, such as a physical device failure or network jitter, occurs in the system without affecting the architecture of the system, thereby promptly resolving the abnormal situation and improving the stability of the system.

[0194] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0195] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0196] The above disclosure is only the preferred embodiment of this specification, which certainly cannot be used to limit the scope of rights of this specification. Therefore, equivalent changes made according to the claims of this specification are still within the scope covered by this specification.

Claims

1. A method for determining system stability, wherein the system comprises at least a sending end device and a receiving end device, and the method is applicable to a sending end device in which a sending end proxy service is deployed in the system, and the method comprises: Obtaining an initial request for instructing the receiving device to provide a service; Generate and set an identifier uniquely representing the initial request for the initial request through the sender proxy service to obtain the request; The request is sent to the receiving end device, so that when the receiving end device receives the request and determines that the identifier set in the request already exists in the historical identifier library, it is determined that no preset abnormal situation occurs in the system.

2. The method for determining system stability according to claim 1, wherein the step of generating and setting an identifier uniquely representing the initial request for the initial request through the sender proxy service to obtain the request comprises: Through the sending end proxy service, bytecode technology is used to generate and dynamically set an identifier that uniquely represents the initial request for the initial request.

3. The method for determining system stability according to claim 2, wherein the sending end proxy service uses bytecode technology to generate and dynamically set an identifier that uniquely represents the initial request for the initial request, comprising: The request is obtained by using the identifier generation technology to generate an identifier that uniquely represents the initial request through the sending-end proxy service, and using bytecode technology to dynamically set the identifier to the initial request; wherein the identifier generation technology includes at least: a snowflake algorithm.

4. The method for determining system stability according to claim 1, wherein the system further comprises: a first routing device and a second routing device; The sending the request to the receiving end device comprises: Sending the request to the receiving device through the first routing device; After sending the request to the receiving end device through the first routing device, the method further includes: When the service provided by the receiving device in response to the request is not received, the request is sent to the receiving device through the second routing device, so that the receiving device receives the request multiple times and determines whether the identifier set in the request already exists in the historical identifier library, so as to determine whether the preset abnormal situation occurs in the system, and the preset abnormal information includes the failure of the first routing device or network jitter.

5. The system stability judgment method according to claim 1, wherein the preset abnormal situation includes at least one of the following situations: a physical device failure in the system and a network jitter.

6. A method for determining system stability, wherein the system comprises at least a transmitting device and a receiving device, and the method is applicable to a receiving device in which a receiving agent service is deployed in the system, and the method comprises: Receiving a request from the transmitting end device; wherein the request is obtained based on the system stability determination method according to any one of claims 1 to 5; By means of the receiving end proxy service, determining whether the identifier set in the request already exists in the historical identifier library; When it is determined that the identifier already exists in the historical identifier library, it is determined that the preset abnormal situation does not occur in the system, and the request is quickly failed.

7. The method for determining system stability according to claim 6, after determining, by the receiving end proxy service, whether the identifier set in the request already exists in the historical identifier library, further comprising: When it is determined that the identifier does not exist in the historical identifier library, the identifier is stored in the historical identifier library, and the service is provided to the sending end device in response to the request.

8. The method for determining system stability according to claim 6, wherein determining, by the receiving end proxy service, whether the identifier set in the request already exists in the historical identifier library comprises: Through the receiving end proxy service, based on the storage engine with strict timing transaction control, it is determined whether the identifier already exists in the historical identifier library.

9. The method for determining system stability according to claim 6, wherein the system further comprises: a first routing device and a second routing device; The receiving a request from the sending end device includes: receiving a request sent from the sending device through the second routing device; After determining whether the identifier set in the request already exists in the historical identifier library, the method further includes: When it is determined that the identifier does not exist in the historical identifier library, it is determined that the preset abnormal situation occurs in the system, and the service is provided to the sending end device in response to the request. The preset abnormal situation includes a failure of the first routing device or a network jitter.

10. A system stability judgment device, the system comprising at least a sending end device and a receiving end device, the device being adapted to be arranged on the sending end device in which a sending end proxy service is deployed in the system, the device comprising: A request acquisition module, used to acquire an initial request for instructing the receiving end device to provide a service; An identification generation module, used to generate and set an identification uniquely representing the initial request for the initial request through the sending end proxy service, so as to obtain a request; The request sending module is used to send the request to the receiving end device, so that when the receiving end device receives the request and determines that the identifier set in the request already exists in the historical identifier library, it determines that no preset abnormal situation occurs in the system.

11. A system stability judgment device, the system comprising at least a sending end device and a receiving end device, the device being adapted to be arranged on the sending end device in which a sending end proxy service is deployed in the system, the device comprising: A request receiving module, used to receive a request from the sending end device; wherein the request is obtained based on the system stability judgment method according to any one of claims 1 to 5; An identification judgment module, used to judge whether the identification set in the request already exists in the historical identification library through the receiving end proxy service; The abnormality judgment module is used to determine that the preset abnormal situation does not occur in the system when it is determined that the identifier already exists in the historical identifier library, and to quickly fail the request.

12. A computer storage medium storing a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 9.

13. A computer program product, wherein the computer program product stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 9.

14. An electronic device comprising: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 9.

Images