WO2021139431A1

WO2021139431A1 - Data synchronization method and apparatus for microservice, electronic device and storage medium

Info

Publication number: WO2021139431A1
Application number: PCT/CN2020/131898
Authority: WO
Inventors: 罗凤宁
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-01-09
Filing date: 2020-11-26
Publication date: 2021-07-15
Also published as: CN111209120A

Abstract

A data synchronization method for a microservice, comprising: on the basis of a pre-constructed consistent hash algorithm, dynamically adding and deleting load balancing scenarios of an original microservice to obtain a standard load balancing scenario, which comprises instance load monitoring of the microservice and instance state change detection of the microservice (S1); reading real-time data from the standard load balancing scenario by means of a pre-created cell server group to obtain a real-time data set (S2); and inputting the real-time data set to cell nodes of the pre-created cell server group to achieve real-time data synchronization among the cell nodes by means of message-oriented middleware (S3). Further provided are a data synchronization apparatus for the microservice, an electronic device and a computer-readable storage medium.

Description

Microservice data synchronization method, device, electronic equipment and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on January 9, 2020, the application number is 2020025271.8, and the invention title is "microservice data synchronization method, device and computer-readable storage medium", and its entire content Incorporated in this application by reference.

Technical field

This application relates to the field of big data technology, and in particular to a data synchronization method, device, electronic device, and storage medium for microservices.

Background technique

Microservice architecture is a new technology for deploying applications and services in the cloud. With the gradual application of microservice architecture, an upstream system will dock with N downstream systems.

technical problem

The inventor realizes that the optimization of upstream systems is limited due to the different standards of each downstream system's response to the interface, the inability of business specificity to cooperate with optimization, and the real-time data synchronization between each system, which leads to the limitation of the optimization of the upstream system, which leads to the degree of coupling between the systems. Too high, the upstream system server pressure is too high, and the upstream system interface response is too slow.

Technical solutions

A data synchronization method for microservices provided in this application includes:

Based on the pre-built consistent hash algorithm, the load balancing scene of the original microservice is dynamically added and deleted to obtain the standard load balancing scene, where the standard load balancing scene includes the instance load monitoring of the microservice and the instance state change detection of the microservice ；

Read real-time data from the standard load balancing scene through a pre-created unit server group to obtain a real-time data set;

The real-time data set is input into the unit nodes of the pre-created unit server group, and real-time data synchronization between the unit nodes is realized through message middleware.

This application provides a data synchronization device for microservices, and the device includes:

Load balancing scene creation module: used to dynamically add and delete load balancing scenes of the original microservices based on a pre-built consistent hash algorithm to obtain a standard load balancing scene, where the standard load balancing scene includes microservice instance load monitoring And microservice instance state change detection;

Real-time data reading module: used to read real-time data from the standard load balancing scene through a pre-created unit server group to obtain a real-time data set;

Real-time data synchronization module: used to input the real-time data set into the unit nodes of the pre-created unit server group, and realize real-time data synchronization between the unit nodes through message middleware.

The present application provides an electronic device that includes a memory and a processor. The memory stores a data synchronization program of a microservice that can run on the processor. The data synchronization program of the microservice is controlled by the processor. The processor executes to implement the following steps:

This application also provides a computer-readable storage medium on which a data synchronization program of a microservice is stored, and the data synchronization program of the microservice can be executed by one or more processors to achieve the following step:

Description of the drawings

FIG. 1 is a schematic flowchart of a data synchronization method for microservices provided by an embodiment of this application;

2 is a schematic diagram of the internal structure of an electronic device provided by an embodiment of the application;

FIG. 3 is a schematic diagram of modules of a microservice data synchronization device provided by an embodiment of the application.

The realization, functional characteristics, and advantages of the purpose of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Embodiments of the present invention

It should be understood that the specific embodiments described here are only used to explain the present application, and are not used to limit the present application.

This application provides a data synchronization method for microservices. Referring to FIG. 1, it is a schematic flowchart of a data synchronization method for microservices provided by an embodiment of this application. The method can be executed by a device, and the device can be implemented by software and/or hardware.

In this embodiment, the data synchronization method for microservices includes:

S1. Based on the pre-built consistent hash algorithm, dynamically add and delete the load balancing scene of the original microservice to obtain the standard load balancing scene, where the standard load balancing scene includes the instance load monitoring of the microservice and the instance status of the microservice Change detection.

In the preferred embodiment of this application, the core idea of the consistent hashing algorithm is to convert the node selection criteria in the common hashing algorithm from a specific value to a range, and the range can be expressed as a closed loop A small continuous range. Further, the pre-built consistent hash algorithm in this application includes: preset number of virtual nodes, constructing the data storage structure of the virtual node, and selecting the hash function of the virtual node.

In detail, the pre-built consistent hash algorithm described in the preferred embodiment of the present application is as follows:

a. Realize the balance of storage space allocation by pre-setting the number of virtual nodes. For example, there are only two physical nodes in a system. If there are no virtual nodes, it is difficult to evenly distribute user requests to these two nodes due to the randomness of the hash algorithm to a certain extent. If the two physical nodes in the system are divided into 200 virtual nodes and mapped to the storage space, and hashing is performed according to the 200 virtual nodes, the balance of storage space allocation can be greatly improved. Therefore, when the system has fewer physical nodes, the number of virtual nodes needs to be increased, and when there are more physical nodes, the number of virtual nodes should be reduced. In this application, a suitable number of virtual nodes can be set according to the number of specific physical nodes.

b. Use the TreeMap data structure in Java to implement the construction of the data storage structure of the virtual node, and the TreeMap data structure implements the storage of the node through a red-black tree.

c. Use the MurMurHash function as the hash function of the virtual node. Wherein, the MurMurHash algorithm refers to a non-cryptographic hash function, and the hash retrieval operation of the virtual node is realized through the MurMurHash function.

Further, the load balancing scenario of the original microservice mentioned in this application refers to amortizing tasks to multiple unit servers for joint completion, where the operation unit may include a Web server, an FTP server, an enterprise key application server, and Other mission-critical servers, etc. The preferred embodiment of the present application implements the dynamic addition and deletion of instances in the load balancing scenario of microservices through the virtual nodes provided by the consistent hash algorithm, and obtains the standard load balancing scenario. For example, each caller sends its request to the same microservice instance as the load balancing scenario of the microservice, where, when the instance crashes and becomes unavailable, the virtual algorithm in the consistent hashing algorithm is changed. The number of nodes can evenly distribute the requests to be received by the instance to other available microservice instances.

Preferably, the standard load balancing scenario described in this application includes instance load monitoring of microservices, and instance state change detection of microservices. In detail, the instance load monitoring of the microservice includes: instance invocation of the microservice, concurrency of the instance of the microservice, and instance data update of the microservice. This application regularly detects whether the instance state change of the microservice is an instance addition and/or deletion through load balancing. When the instance state change of the microservice is the addition and/or deletion of the instance, the consistent hash algorithm is used to reallocate the instance request, and the allocation result is returned to the corresponding caller; when the instance of the microservice When the status change is not an instance addition and/or deletion, report the running load status of the instance, and periodically determine whether the load status of the instance reaches the preset load threshold, and when the preset load threshold is not reached, No request adjustment is made. When the preset load threshold is reached, the partial requests of the microservice instances are evenly distributed to other microservice instances that do not exceed the load threshold, and the load threshold is determined according to the load. Balancing the results of timing detection, the caller can modify the local cached microservice address information, thereby reducing the coupling between systems.

S2. Read real-time data from the standard load balancing scene through the pre-created unit server group to obtain a real-time data set.

In the preferred embodiment of the present application, the unit server group is constructed through Redis in the load balancing scenario of the microservice. The Redis is an open source, memory-based key-value pair storage system that provides rich data structures such as strings, lists, sets, and hash objects. Preferably, the construction of the unit server through Redis in this application includes: constructing the storage data structure of the unit server, selecting the unit server persistence mode, and using the replication function of Redis to realize the data backup of the unit server And storing the fixed data of the unit server.

Further, the constructing the storage data structure of the unit server includes: using the data type provided by Redis to select the data structure to facilitate classified storage and rapid retrieval. Since the key value provided by Redis supports the function of binary security, any form of binary sequence can be used in the selection of the form of the key in this application. For example, the form of the key for the state attribute of the microservice instance can be set to the string "microservice:instance:state:instanceId", and the real-time location information of the microservice instance can be set to the string "service_id:instance_id:url". The key pattern formed by the multiple fields and symbol intervals has good structure, and can quickly classify and search data in Redis.

Further, the selecting the unit server persistence mode includes: performing data persistence through the AOF (Append Only File) persistence mode in Redis. The AOF saves the write commands executed by the Redis to persist the state of the database, and also provides an AOF rewrite mechanism to reduce Redundancy in AOF files, thereby improving storage efficiency.

Further, the use of the replication function of Redis to implement the data backup of the unit server includes: selecting a certain unit server among the unit servers as the master unit server, and setting the remaining unit servers through the Redis command and slaveof configuration attributes Set as the slave unit server of the master unit server; after the slave unit server is started, a synchronization command is sent to the master unit server, and a background process is started by the master unit server to generate a snapshot of memory data, and at the same time it is recorded in the generation The newly executed write command during the snapshot completes the data backup of the main unit server. If there are multiple slave unit servers requesting synchronization at the same time, the master unit server only needs to execute the bgsave command once to process the synchronization requests of the multiple slave unit servers.

Further, storing the fixed data of the unit server in combination with MySQL includes: storing fixed data in microservice attributes in combination with MySQL. The fixed data may be the name attribute, version attribute, capacity attribute, and provider information of the microservice. Wait.

Further, the unit server constructed according to the preferred embodiment of the present application can read real-time data to the load balancing scene of the microservice to obtain a real-time data set, wherein the unit server can support high-concurrency data Reading operation improves the response speed of the system.

S3. Input the real-time data set into the unit nodes of the pre-created unit server group, and realize real-time data synchronization between the unit nodes through message middleware.

In a preferred embodiment of the present application, the unit node is constructed in the unit server group according to the attributes of real-time data and the needs of users. The attributes of the real-time data can be field names, parameter types, etc., and the user The demand can be to obtain data in real time, not to obtain data in real time, etc. Preferably, the message middleware in this application is MQ message middleware, and the MQ message middleware refers to those that can effectively guarantee and support the sending and receiving of messages through a synchronous or asynchronous mechanism in a distributed application system. Middleware system. The real-time data synchronization between the pre-built unit nodes can be realized through the MQ message middleware, thereby ensuring data consistency in a microservice-based scenario.

The invention also provides an electronic device. Referring to FIG. 2, it is a schematic diagram of the internal structure of an electronic device provided by an embodiment of this application.

In this embodiment, the electronic device 1 may be a PC (Personal Computer, personal computer), or a data processing device such as a smart phone, a tablet computer, or a portable computer, or a server or the like. The electronic device 1 at least includes a memory 11, a processor 12, a communication bus 13, and a network interface 14.

The memory 11 includes at least one type of readable storage medium. The readable storage medium may be non-volatile or volatile. The readable storage medium includes flash memory, hard disk, multimedia card, and card type. Storage (for example, SD or DX storage, etc.), magnetic storage, magnetic disk, optical disk, etc. The memory 11 may be an internal storage unit of the electronic device 1 in some embodiments, such as a hard disk of the electronic device 1. In other embodiments, the memory 11 may also be an external storage device of the electronic device 1, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), and a secure digital (Secure Digital, SD) equipped on the electronic device 1. Flash memory card Card) and so on. Further, the memory 11 may also include both an internal storage unit of the electronic device 1 and an external storage device. The memory 11 can be used not only to store application software and various types of data installed in the electronic device 1, such as the code of a data synchronization program for microservices, etc., but also to temporarily store data that has been output or will be output.

The processor 12 may be a central processing unit (Central Processing Unit) in some embodiments. Processing Unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips are used to run program codes or process data stored in the memory 11, such as executing data synchronization programs for microservices.

The communication bus 13 is used to realize the connection and communication between these components.

The network interface 14 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface), and is usually used to establish a communication connection between the apparatus 1 and other electronic devices.

Optionally, the electronic device 1 may further include a user interface. The user interface may include a display (Display) and an input unit such as a keyboard (Keyboard). The optional user interface may also include a standard wired interface and a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an OLED (Organic Light-Emitting Diode, organic light-emitting diode) touch device and so on. Among them, the display can also be appropriately called a display screen or a display unit, which is used to display the information processed in the electronic device 1 and to display a visualized user interface.

Figure 2 only shows the electronic device 1 with components 11-14 and a data synchronization program for microservices. Those skilled in the art can understand that the structure shown in Figure 2 does not constitute a limitation on the electronic device 1, and may include Fewer or more parts than shown, or some parts in combination, or different parts arrangement.

In the embodiment of the electronic device 1 shown in FIG. 2, the data synchronization program of the microservice is stored in the memory 11; when the processor 12 executes the data synchronization program of the microservice stored in the memory 11, the following steps are implemented:

Step 1. Based on the pre-built consistent hash algorithm, dynamically add and delete the load balancing scene of the original microservice to obtain a standard load balancing scene, where the standard load balancing scene includes instance load monitoring of microservices and instances of microservices State change detection.

b. Adopt The TreeMap data structure in Java implements the construction of the data storage structure of the virtual node, and the TreeMap data structure implements the storage of the node through a red-black tree.

Step 2: Read real-time data from the standard load balancing scene through the pre-created unit server group to obtain a real-time data set.

The preferred embodiment of the present application is based on the construction of the unit server group through Redis in the load balancing scenario of the microservice. The Redis is an open source, memory-based key-value pair storage system that provides rich data structures such as strings, lists, sets, and hash objects. Preferably, the construction of the unit server through Redis in this application includes: constructing the storage data structure of the unit server, selecting the unit server persistence mode, and using the replication function of Redis to realize the data backup of the unit server And storing the fixed data of the unit server.

Step 3: Input the real-time data set into the unit nodes of the pre-created unit server group, and realize real-time data synchronization between the unit nodes through message middleware.

Referring to Figure 3, this is a schematic diagram of modules in an embodiment of the data synchronization device 2 for microservices of this application. In this embodiment, the data synchronization device for microservices can be divided into a load balancing scene creation module 10 and real-time data. The reading module 20 and the real-time data synchronization module 30 are exemplary:

The load balancing scene creation module 10 is used to dynamically add and delete load balancing scenes of the original microservices based on a pre-built consistent hash algorithm to obtain a standard load balancing scene, where the standard load balancing scene includes microservices Instance load monitoring and microservice instance status change detection.

The real-time data reading module 20 is configured to read real-time data from the standard load balancing scene through a pre-created unit server group to obtain a real-time data set.

The real-time data synchronization module 30 is configured to input the real-time data set into the unit nodes of the pre-created unit server group, and realize real-time data synchronization between the unit nodes through message middleware.

The functions or operation steps implemented by the program modules such as the load balancing scenario creation module 10, the real-time data reading module 20, and the real-time data synchronization module 30 when executed are substantially the same as those in the foregoing embodiment, and will not be repeated here.

Preferably, the load balancing scenario creation module 10, the real-time data reading module 20, and the real-time data synchronization module 30 described in this application can form a micro-service data synchronization system, such as an APP that can be installed on a user's mobile phone or computer.

In addition, the embodiment of the present application also proposes a computer-readable storage medium. The computer-readable storage medium may be non-volatile or volatile, and the computer-readable storage medium stores microservice data. A synchronization program. The data synchronization program of the microservice can be executed by one or more processors to achieve the following operations:

The specific implementation of the computer-readable storage medium of this application is basically the same as the above-mentioned embodiments of the microservice data synchronization device and method, and will not be repeated here.

It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description, and do not represent the superiority or inferiority of the embodiments. And the terms "include", "include" or any other variants thereof in this article are intended to cover non-exclusive inclusion, so that a process, device, article or method including a series of elements not only includes those elements, but also includes those elements that are not explicitly included. The other elements listed may also include elements inherent to the process, device, article, or method. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, device, article, or method that includes the element.

Through the description of the above implementation manners, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM) as described above. , Magnetic disks, optical disks), including several instructions to make a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) execute the method described in each embodiment of the present application.

The above are only the preferred embodiments of the application, and do not limit the scope of the patent for this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of the application, or directly or indirectly applied to other related technical fields , The same reason is included in the scope of patent protection of this application.

Claims

A data synchronization method for microservices, wherein the method includes:

Based on the pre-built consistent hash algorithm, the load balancing scene of the original microservice is dynamically added and deleted to obtain the standard load balancing scene, where the standard load balancing scene includes the instance load monitoring of the microservice and the instance state change detection of the microservice ；

Read real-time data from the standard load balancing scene through a pre-created unit server group to obtain a real-time data set;

The real-time data set is input into the unit nodes of the pre-created unit server group, and real-time data synchronization between the unit nodes is realized through message middleware.
The data synchronization method for microservices according to claim 1, wherein the pre-built consistent hashing algorithm comprises:

Preset the number of virtual nodes to achieve a balanced distribution of storage space;

Using the TreeMap data structure to construct the data storage structure of the virtual node, the TreeMap data structure implements the storage of the node through a red-black tree;

The hash function of the virtual node is selected, and the hash retrieval operation of the virtual node is realized through the hash function.
The method for data synchronization of microservices according to claim 1, wherein the load balancing scenario of the original microservice includes allocating tasks to multiple unit servers for joint completion, wherein the operation unit includes a Web server, an FTP server , Enterprise key application server.
The microservice data synchronization method according to any one of claims 1 to 3, wherein the instance load monitoring of the microservice includes: instance invocation of the microservice, concurrency of the instance of the microservice, and update of the instance data of the microservice .
The data synchronization method of a microservice according to any one of claims 1 to 3, wherein the detection of the instance state change of the microservice comprises:

Periodically detecting whether the instance state change of the microservice is an instance addition and/or deletion through load balancing;

When the instance state of the microservice changes as an instance is added and/or deleted, the consistent hash algorithm is used to reallocate the instance request, and the allocation result is returned to the corresponding caller;

When the instance status change of the microservice is not an instance addition and/or deletion, the load status of the instance operation is reported, and it is periodically determined whether the load status of the instance reaches a preset load threshold.
The data synchronization method for microservices according to any one of claims 1 to 3, wherein the method further comprises:

Construct the storage data structure of the unit server group, select the persistence mode of the unit server group, use the replication function of Redis to realize the data backup of the unit server group and store the fixed data of the unit server group to complete the Creation of a cell server group.
7. The data synchronization method for microservices according to claim 6, wherein said using the replication function of Redis to implement data backup of said unit server group comprises:

Select one of the unit servers in the unit server group as the master unit server, and set the remaining unit servers in the unit server group as the slave unit servers of the master unit server through the laveof command and slaveof configuration attribute of the Redis;

Start the slave unit server, send a synchronization command to the master unit server, start a background process through the master unit server to generate a snapshot of the memory data, and record the newly executed write commands during the snapshot generation to complete the unit server Data backup of the main unit server in the group.
A data synchronization device for microservices, wherein the device includes:

Load balancing scene creation module: used to dynamically add and delete load balancing scenes of the original microservices based on a pre-built consistent hash algorithm to obtain a standard load balancing scene, where the standard load balancing scene includes microservice instance load monitoring And microservice instance state change detection;

Real-time data reading module: used to read real-time data from the standard load balancing scene through a pre-created unit server group to obtain a real-time data set;

Real-time data synchronization module: used to input the real-time data set into the unit nodes of the pre-created unit server group, and realize real-time data synchronization between the unit nodes through message middleware.
An electronic device, wherein the electronic device includes a memory and a processor, the memory stores a data synchronization program of a microservice that can be run on the processor, and the data synchronization program of the microservice is The processor executes to achieve the following steps:

Based on the pre-built consistent hash algorithm, the load balancing scene of the original microservice is dynamically added and deleted to obtain the standard load balancing scene, where the standard load balancing scene includes the instance load monitoring of the microservice and the instance state change detection of the microservice ；

Read real-time data from the standard load balancing scene through a pre-created unit server group to obtain a real-time data set;

The real-time data set is input into the unit nodes of the pre-created unit server group, and real-time data synchronization between the unit nodes is realized through message middleware.
9. The electronic device of claim 9, wherein the pre-built consistent hashing algorithm comprises:

Preset the number of virtual nodes to achieve a balanced distribution of storage space;

Using the TreeMap data structure to construct the data storage structure of the virtual node, the TreeMap data structure implements the storage of the node through a red-black tree;

The hash function of the virtual node is selected, and the hash retrieval operation of the virtual node is realized through the hash function.
The electronic device according to claim 9, wherein the load balancing scenario of the original microservice includes allocating tasks to a plurality of unit servers for joint completion, wherein the operation unit includes a Web server, an FTP server, and a key enterprise application server.
The electronic device according to any one of claims 9 to 11, wherein the instance load monitoring of the microservice includes: instance invocation of the microservice, concurrency of the instance of the microservice, and instance data update of the microservice.
The electronic device according to any one of claims 9 to 11, wherein the detection of the instance state change of the microservice comprises:

Periodically detecting whether the instance state change of the microservice is an instance addition and/or deletion through load balancing;

When the instance state of the microservice changes as an instance is added and/or deleted, the consistent hash algorithm is used to reallocate the instance request, and the allocation result is returned to the corresponding caller;

When the instance status change of the microservice is not an instance addition and/or deletion, the load status of the instance operation is reported, and it is periodically determined whether the load status of the instance reaches a preset load threshold.
The electronic device according to any one of claims 9 to 11, wherein the execution of the data synchronization program of the microservice by the processor further implements the following steps:

Construct the storage data structure of the unit server group, select the persistence mode of the unit server group, use the replication function of Redis to realize the data backup of the unit server group and store the fixed data of the unit server group to complete the Creation of a cell server group.
The electronic device according to claim 14, wherein said using the replication function of Redis to realize the data backup of the unit server group comprises:

Select one of the unit servers in the unit server group as the master unit server, and set the remaining unit servers in the unit server group as the slave unit servers of the master unit server through the laveof command and slaveof configuration attribute of the Redis;

Start the slave unit server, send a synchronization command to the master unit server, start a background process through the master unit server to generate a snapshot of the memory data, and record the newly executed write commands during the snapshot generation to complete the unit server Data backup of the main unit server in the group.
A computer-readable storage medium, wherein a data synchronization program of a microservice is stored on the computer-readable storage medium, and the data synchronization program of the microservice can be executed by one or more processors to implement the following steps:

Based on the pre-built consistent hash algorithm, the load balancing scene of the original microservice is dynamically added and deleted to obtain the standard load balancing scene, where the standard load balancing scene includes the instance load monitoring of the microservice and the instance state change detection of the microservice ；

Read real-time data from the standard load balancing scene through a pre-created unit server group to obtain a real-time data set;

The real-time data set is input into the unit nodes of the pre-created unit server group, and real-time data synchronization between the unit nodes is realized through message middleware.
15. The computer-readable storage medium of claim 16, wherein the pre-built consistent hashing algorithm comprises:

Preset the number of virtual nodes to achieve a balanced distribution of storage space;

Using the TreeMap data structure to construct the data storage structure of the virtual node, the TreeMap data structure implements the storage of the node through a red-black tree;

The hash function of the virtual node is selected, and the hash retrieval operation of the virtual node is realized through the hash function.
16. The computer-readable storage medium according to claim 16, wherein the load balancing scenario of the original microservice includes allocating tasks to multiple unit servers for joint completion, wherein the operation unit includes a Web server, an FTP server, Enterprise critical application server.
The computer-readable storage medium according to any one of claims 16 to 18, wherein the instance load monitoring of the microservice includes: instance invocation of the microservice, concurrency of the instance of the microservice, and instance data update of the microservice.
The computer-readable storage medium according to any one of claims 16 to 18, wherein the detection of the instance state change of the microservice comprises:

Periodically detecting whether the instance state change of the microservice is an instance addition and/or deletion through load balancing;

When the instance state of the microservice changes as an instance is added and/or deleted, the consistent hash algorithm is used to reallocate the instance request, and the allocation result is returned to the corresponding caller;

When the instance status change of the microservice is not an instance addition and/or deletion, the load status of the instance operation is reported, and it is periodically determined whether the load status of the instance reaches a preset load threshold.