WO2021203968A1

WO2021203968A1 - Method for unified management of micro-services of multiple registration centers, and apparatus, device and medium

Info

Publication number: WO2021203968A1
Application number: PCT/CN2021/082595
Authority: WO
Inventors: 吴超勇
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-10-28
Filing date: 2021-03-24
Publication date: 2021-10-14
Also published as: CN112286503A

Abstract

A method for the unified management of micro-services of multiple registration centers, and an apparatus, a device and a medium. The method comprises: dividing micro-services into different micro-service modes according to a preset condition (S110); dynamically triggering a service discovery mechanism according to changes in service states of the micro-services, and acquiring service information of the different micro-service modes (S120); by means of a preset unified encoding rule, converting the service information of the different micro-service modes into service codes in a unified format, and storing same in a service registry (S130); and performing intelligent parsing on the service codes in the unified format so as to match corresponding micro-services, and then encapsulating same into corresponding application program interfaces for consumption by consumers (S140). The problem of data collaboration between multiple sets of different registration centers can be effectively solved. The coupling of micro-service collaborative management between multiple frameworks is reduced, thereby facilitating the unified management of micro-services, and reducing the operation and maintenance costs.

Description

Multi-registration center microservice unified management method, device, equipment and medium

This application requires the priority of a Chinese patent application filed with the Chinese Patent Office on October 28, 2020, the application number is 202011175929.X, and the invention title is "Multi-registration center microservice unified management method, device, equipment and medium". The entire content is incorporated into the application by reference.

Technical field

This application relates to the technical field of scaffolding operation and maintenance, and in particular to a method, device, equipment, and medium for unified management of microservices with multiple registration centers.

Background technique

Microservice registration is an extremely important module in the field of microservice architecture. For complex IT systems, the quality of the microservice registration mechanism directly affects the availability, segmentation tolerance, and data consistency of the entire system. The choice of a general registry is strongly related to the service framework. A common situation is that a service framework will bring a default service registry. The inventor realized that although this saves users from the trouble of selection, a single registry Due to the limitations of, when users use multiple service frameworks, they must deploy multiple sets of completely different registries. The data coordination between these registries is a problem.

Summary of the invention

In view of this, a unified management method for microservices with multiple registries is provided to solve the problem of data coordination between multiple sets of completely different registries.

In order to achieve the above objective, the first aspect of this application provides a method for unified management of microservices with multiple registration centers, including: dividing microservices into different microservice modes according to preset conditions; Change, dynamically trigger the service discovery mechanism to obtain the service information of the different microservice modes; convert the service information of the different microservice modes into a unified format service code through a preset unified coding rule, and store it in the service registration In the table; intelligent analysis of the uniform format of the service code to match the corresponding microservices, and encapsulate the corresponding application program interface for consumption by the consumer.

The second aspect of the present application provides a multi-registration center microservice unified management device, including a memory, a processor, and computer-readable instructions stored on the memory and running on the processor. The processor The following steps are implemented when the computer-readable instructions are executed: the microservices are divided into different microservice modes according to preset conditions; the service discovery mechanism is dynamically triggered according to the changes in the service status of the microservices, and the different microservices are obtained. The service information of the service mode; the service information of the different microservice modes is converted into a service code of a unified format through preset unified coding rules, and stored in the service registry; the service code of the unified format is intelligently analyzed Match the corresponding microservices and encapsulate them into corresponding application program interfaces for consumption by consumers.

The third aspect of the present application provides a computer-readable storage medium that stores computer instructions. When the computer instructions run on the computer, the computer executes the following steps: Microservices are divided into different microservice modes; according to changes in the service status of the microservices, the service discovery mechanism is dynamically triggered to obtain the service information of the different microservice modes; and the service information of the different microservice modes After preset unified coding rules, it is transformed into a unified format service code and stored in the service registry; the unified format service code is intelligently analyzed to match the corresponding microservice, and packaged into a corresponding application program interface for consumers Make consumption.

The fourth aspect of the present application provides a unified management device for microservices with multiple registration centers, including: a division module for dividing microservices into different microservice modes according to preset conditions; a service information acquisition module for The change of the service status of the microservices dynamically triggers the service discovery mechanism to obtain the service information of the different microservice modes; the unified coding module is used to pass the service information of the different microservice modes through preset unified coding rules The service code is converted into a unified format and stored in the service registry; the application module is used to intelligently analyze the service code of the unified format to match the corresponding microservice, and encapsulate it into a corresponding application program interface for the consumer to perform Consumption.

One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages: dividing microservices into different microservice modes according to preset conditions; dividing the microservice modes for subsequent acquisition of service information and It is possible to uniformly code service information. According to the change of the service status of the microservice, the service discovery mechanism is dynamically triggered to obtain the service information of the different microservice modes; the service information of the different microservice modes is obtained to provide data for subsequent unified coding in accordance with the unified coding rules support. The service information of the different microservice modes is converted into a unified format service code through preset unified coding rules, and stored in the service registry; a service management mechanism compatible with various protocol services can greatly reduce the structure The consumption of each component in subsequent calls enhances the overall stability and usability. The service code in the unified format is intelligently analyzed and matched to the corresponding microservice, and encapsulated into a corresponding application program interface for consumption by the consumer. It can effectively solve the problem of data coordination between multiple sets of completely different registration centers. When users use multiple service frameworks, they are no longer strongly dependent on the limitations of a single registry, which reduces the coupling of microservice collaborative management between multiple frameworks, facilitates the unified management of microservices, and reduces operation and maintenance costs.

Description of the drawings

FIG. 1 is a schematic diagram of the hardware architecture of the method for unified management of microservices with multiple registration centers involved in an embodiment of the application;

2 is a schematic flowchart of a first embodiment of a method for unified management of microservices with multiple registration centers of the application;

Figure 3 is a work flow chart of applying for a unified management method of microservices with multiple registration centers;

4 is a schematic diagram of the specific flow of step S130 in the first embodiment of the second embodiment of the method for unified management of microservices with multiple registration centers under this application;

FIG. 5 is a schematic diagram of the specific flow of step S130 in the first embodiment of the method for unified management of microservices with multiple registration centers under this application;

6 is a schematic diagram of the specific flow of step S140 in the first embodiment of the method for unified management of microservices with multiple registration centers under this application;

FIG. 7 is a schematic diagram of the specific flow of step S110 in the first embodiment of the method for unified management of microservices with multiple registration centers under this application;

FIG. 8 is a schematic flowchart of a second embodiment of a method for unified management of microservices with multiple registration centers of the application;

FIG. 9 is a schematic structural diagram of an apparatus for a unified management method for microservices with multiple registration centers according to the present application.

Detailed ways

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.

The main solution of the embodiment of the present application is: divide microservices into different microservice modes according to preset conditions; dynamically trigger a service discovery mechanism according to changes in the service status of the microservices, and obtain the different microservice modes The service information of the different microservice modes; the service information of the different microservice modes is converted into a service code of a unified format through preset unified coding rules, and stored in the service registry; the service code of the unified format is intelligently parsed and matched The microservices are packaged into corresponding application program interfaces for consumption by consumers. It can effectively solve the problem of data coordination between multiple sets of completely different registration centers. When users use multiple service frameworks, they are no longer strongly dependent on the limitations of a single registry, which reduces the coupling of microservice collaborative management between multiple frameworks, facilitates the unified management of microservices, and reduces operation and maintenance costs.

In order to better understand the above technical solutions, the above technical solutions will be described in detail below in conjunction with the accompanying drawings of the specification and specific implementations.

This application relates to a device including as shown in FIG. 1: at least one processor 12 and a memory 11.

The processor 12 may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the foregoing method may be completed by an integrated logic circuit of hardware in the processor 12 or instructions in the form of software. The above-mentioned processor 12 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware Components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like. The software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory 11, and the processor 12 reads the information in the memory 11, and completes the steps of the above method in combination with its hardware.

It can be understood that the memory 11 in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read only memory (Read Only Memory, ROM), programmable read only memory (Programmable ROM, PROM), erasable programmable read only memory (Erasable PROM, EPROM), and electrically erasable Except for programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. By way of exemplary but not restrictive description, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synchronous Link Dynamic Random Access Memory (Synch link DRAM, SLDRAM) ) And Direct Rambus RAM (DRRAM). The memory 11 of the system and method described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

Referring to Figure 2, Figure 2 is a first embodiment of a method for unified management of microservices with multiple registries under this application. The method for unified management of microservices with multiple registries includes the following steps:

Step S110: Divide the microservices into different microservice modes according to preset conditions.

The preset condition is to divide microservices into different microservice modes according to different integration modes or calling protocols. There can be multiple microservice modes. The preset conditions are not limited here, and other division methods may also be used.

Microservice (or microservice architecture) is a cloud-native architecture method in which a single application consists of many smaller components or services that are loosely coupled and independently deployable. These services usually have their own stack, including databases and data models; they communicate with each other through a combination of application program interfaces, event streams, and message brokers; they are organized by business capabilities, and the lines separating services are usually called bounded contexts. Under the microservice architecture, there are three main roles: service provider, service consumer, and service registry.

The service registry (Registry) is a database that stores service instances. A service registry should be highly available and the data should be up-to-date. After the consumer queries the service registry, it will cache part of the network address data.

Each registry corresponds to multiple service instances, and the multiple service instances corresponding to each registry use the same integration mode or the same calling protocol or the same attributes.

Step S120: According to the change of the service status of the microservice, a service discovery mechanism is dynamically triggered to obtain the service information of the different microservice modes.

Service status is used to monitor changes in the service status of microservices, including service offline events, service registration events, service renewal events, registry startup events, and startup events. When any of the above service status changes are monitored, The service discovery mechanism is triggered dynamically.

The service discovery mechanism can be a mechanism by which the consumer of the service discovers the provider of the service. The core of the service discovery mechanism model is the proxy and the position of the proxy in the architecture. An agent is added between the service consumer and the service provider. The agent is responsible for service discovery, and the consumer indirectly accesses the target service through the agent. According to the different location of the agent structure, it can be divided into three different service discovery modes: traditional centralized agent, client embedded agent, and host independent process agent.

In this embodiment, this application adopts a service discovery mechanism that combines a traditional centralized agent and a service registry to reduce the complexity of manual configuration. When the service starts, it will automatically register to the service registry and report the heartbeat regularly, and the agent will periodically synchronize the service instance to the service registry. Under this service discovery mechanism, there is no need to apply for a domain name for each service, only a generic domain name is required.

Step S130: The service information of the different microservice modes is converted into a service code of a unified format through a preset unified coding rule, and stored in the service registry.

Service information is an attribute corresponding to each service instance, and it can be one or multiple.

After a preset uniform coding rule is converted into a uniform format service code, the uniform coding rule does not limit what is proposed in this application, and may also be other uniform coding rules.

Step S140: Perform intelligent analysis on the service code in the unified format to match the corresponding microservice, and encapsulate it into a corresponding application program interface for consumption by the consumer.

API (Application Programming Interface) is some pre-defined functions, or refers to the agreement of the connection of different components of the software system. It is used to provide a set of routines that applications and developers give to certain software or hardware to access without having to access the source code or understand the details of the working mechanism of the content.

In this embodiment, the service code in the unified format is intelligently analyzed to match the corresponding microservice, and packaged into a corresponding application program interface for consumption by the consumer. The consumer does not need to access the source code nor understand the working mechanism of the microservice. For details, directly use the API interface for consumption, which can effectively solve the problem of data coordination between multiple sets of completely different registries.

The beneficial effect existing in the above-mentioned embodiment: FIG. 3 is a work flow chart of a method for unified management of microservices with multiple registration centers. Divide microservices into different microservice modes according to preset conditions; divide the microservice modes to provide the possibility for subsequent acquisition of service information and uniform coding of service information. According to the change of the service status of the microservice, the service discovery mechanism is dynamically triggered to obtain the service information of the different microservice modes; the service information of the different microservice modes is obtained to provide data for subsequent unified coding in accordance with the unified coding rules support. The service information of the different microservice modes is converted into a service code of a unified format through preset unified coding rules, and stored in the service registry; a service management mechanism compatible with various protocol services can greatly reduce the structure The consumption of each component in subsequent calls enhances the overall stability and usability. The service code in the unified format is intelligently analyzed and matched to the corresponding microservice, and encapsulated into a corresponding application program interface for consumption by the consumer. It can effectively solve the problem of data coordination between multiple sets of completely different registration centers. When users use multiple service frameworks, they are no longer strongly dependent on the limitations of a single registry, which reduces the coupling of microservice collaborative management between multiple frameworks, facilitates the unified management of microservices, and reduces operation and maintenance costs.

In one of the embodiments, the service information is an attribute corresponding to a service instance in each registry, and the attribute includes at least one of the following: Internet Protocol address, port number, whether it is a temporary service instance, and is used to select the best The weight, health status, and metadata of the service instance invocation.

Internet Protocol Address (Internet Protocol Address) refers to IP address, which is also translated as Internet Protocol address.

The IP address is a unified address format provided by the IP protocol. It assigns a logical address to each network and each host on the Internet to shield differences in physical addresses.

The so-called port is like a house number. The client can find the corresponding server through the IP address, but the server has many ports. Each application corresponds to a port number. Through the port number similar to the house number, the client Only the end can actually access the server. In order to distinguish the ports, each port is numbered. This is the port number.

The network locations of service instances are dynamically allocated, and service instances often change dynamically due to requirements such as expansion, failure, and upgrade. Some service instances may be temporary service instances, so this attribute determines whether the corresponding service instance is a temporary service instance.

It is used to select the weight of the optimal service instance call. By default, the weight of each service instance is calculated every 30 seconds. If the average response time of a service is shorter, the weight is greater, and then the service instance is selected to perform the task. The probability is greater.

The health status can provide information about the status of the server running the microservice instance, or it can be an indicator of whether the microservice is running, so that a richer monitoring experience can be obtained.

Metadata can be the default data of the microservice model or custom data.

The above-mentioned embodiment has the beneficial effect: by obtaining the attribute corresponding to the service instance in each registry in the service information, providing data support for the unified coding rule is a necessary condition for the unified coding.

Referring to Figure 4, Figure 4 is a schematic diagram of the specific flow of step S130 in the first embodiment of the method for unified management of microservices with multiple registration centers under this application. The service information of the different microservice modes is subjected to preset uniform coding rules. The service code transformed into a unified format, including:

Step S131: Select the attribute applied to the unified coding rule.

Step S132: preset the number of coding bits corresponding to the selected attributes.

Step S133: Concatenate the selected attributes in a preset order to obtain the service code in the unified format.

In this embodiment, the preset unified encoding rule may be that the unified encoding consists of 20 decimal digits and consists of an IP address (taking IPv4 as an example, the text format of the address is nnn.nnn.nnn.nnn, which occupies 12 digits in total) , Port number (XXXX, a total of 4), whether it is a temporary service instance (1 digit), weight (1 digit), health status (1 digit) and metadata (2 digits), that is, the default uniform code = IP address + port number + whether it is a temporary service instance + weight + health status + metadata. After preset uniform coding rules, the service information of different microservice modes can be converted into uniform format service codes.

The preset order of service instance attributes in the preset coding rules can be dynamically adjusted, which is not limited here. For example: the preset encoding rule can be a unified encoding consisting of 20 decimal digits, port (XXXX, a total of 4), IP address (taking IPv4 as an example, the text format of the address is nnn.nnn.nnn.nnn, A total of 12 digits), weight (1 digit), whether it is a temporary service instance (1 digit), health status (1 digit), and metadata (2 digits), that is, the default unified code = port + IP address +Weight+Whether it is a temporary service instance+Health status+Metadata. After preset uniform coding rules, the service information of different microservice modes can be converted into uniform format service codes.

Here, the IP address can also be in the IPv6 format, and the number of characters in the unified encoding rule is preset for adaptive adjustment to ensure that the unified encoding can be performed.

The above-mentioned embodiment has the beneficial effect: the service information of the different microservice modes is converted into a service code of a unified format through preset unified coding rules, which can be compatible with various service modes. The service management mechanism can greatly reduce the structure The consumption of each component in subsequent calls enhances the overall stability and usability.

Referring to FIG. 5, FIG. 5 is a schematic diagram of the specific process of step S130 in the first embodiment of the method for unified management of microservices with multiple registration centers of this application. The service information of the different microservice modes is subjected to preset unified coding rules The service code converted into a unified format also includes:

Step S131': Select the attribute applied to the unified coding rule.

Step S132': preset the number of coding bits corresponding to the selected attributes.

Step S133': the selected attributes are concatenated according to the preset order to obtain the service code in the unified format.

Step S134': When the attribute selected in the uniform coding rule is missing in the service information, perform a zero-padded operation on the missing attribute.

The attributes of the service information in the uniform coding rule can be the complete set of service instance attributes in different microservice modes. For example, the uniform coding rule is IP address + port + weight + health status + metadata, and the attribute of a service instance includes IP 192.168. 1.1, the port is 0066, and the weight is 0.2, then the uniform code of the service instance should be 192.168.001.001+0066+0.2+0+00 (zero padding for health status and metadata). If the attributes of a service instance include the IP of 192.168.2.1 and the health status of 1, the uniform code of the service instance should be 192.168.002.001+0000+0+1+00 (port, weight, and metadata are zero-filled). Among them, the health status can be 1 or 0 to indicate two states.

The foregoing embodiment includes step S131', step S132', and step S133', which will not be repeated here.

The above is the beneficial effect of the embodiment: when the selected attribute in the uniform coding rule is missing in the service information, the step of zero-filling the missing attribute is added to ensure the correctness and comprehensiveness of the uniform coding rule. sex.

Referring to Fig. 6, Fig. 6 is a schematic diagram of the specific flow of step S140 in the first embodiment of the method for unified management of microservices with multiple registration centers of this application. The intelligent analysis of the service code in the unified format includes:

Step S141: Acquire the service code in the unified format corresponding to the service name from the service registration table in real time.

Establish a service registry, that is, a database that includes services, service instances and their location information. Each service instance needs to be registered to the service registry when it is started, and to be deregistered when it is shut down. The client and/or router of the service can find available service instances by querying the service registry.

There are two modes for service instance registration in the service registry, self-registration mode and third-party registration mode.

The self-registration mode is that the service instance completes the registration by itself. In the third-party registration mode, the third-party registration tool registers each service instance to the service registry. In this embodiment, the third-party registration mode is selected to store the service code in the uniform format obtained after encoding in the service registry. The third-party registration tool can correspondingly adjust the service code in the uniform format obtained after encoding, according to the uniform format of the service code. The service code is stored to provide more reliable data support for subsequent intelligent analysis.

The consumer can propose the microservice to be called by the service name, or other methods, such as IP address and other attributes that can uniquely determine the location of the microservice, which makes it more convenient for the consumer to call the required microservice, which is not limited here.

Step S142: According to the number of code bits corresponding to each attribute, the corresponding attributes are sequentially acquired.

The service code in the uniform format corresponding to the service name is obtained from the service registration table in real time, and then according to the service coding format, the number of coding bits corresponding to each attribute, and the coding sequence corresponding to each attribute, the number of service instances in the service code The attributes are extracted. For example, the uniform code of the service instance can be 192.168.001.001+6060+0.2+0+00, then the attribute of the service instance extracted by the corresponding intelligent analysis is 192.168.1.1, the port is 0066, and the weight is 0.2. According to the extracted The attributes of the service instance come out to execute the corresponding microservice.

The beneficial effects in the above embodiments: intelligently analyze the service code in the unified format to match the corresponding microservices, provide data support for the encapsulated application program interface, and ensure that the attributes obtained by the intelligent analysis are consistent with the encapsulated application program interface. Correctness.

In one of the embodiments, the attribute that the selection is applied to the unified coding rule includes:

The full set of attributes corresponding to each service instance is selected to be applied to the unified coding rule.

For example, if the attributes of a service instance include IP 192.168.1.1, port 0066, and weight 0.2, while another service instance attribute includes IP 192.168.2.1 and health status 1, then the attributes in the uniform coding rule include IP and port , Weight, health status, the dynamic adjustment of the unified coding sequence is not limited.

The beneficial effect existing in the above-mentioned embodiment is that the full set of attributes corresponding to each service instance is selected to be applied to the unified coding rule so that any service instance can be uniformly coded and converted into a service code of a unified format.

Referring to FIG. 7, FIG. 7 is a schematic diagram of the specific process of step S110 in the first embodiment of the method for unified management of microservices with multiple registration centers of this application. The division of microservices into different microservice modes according to preset conditions includes:

Step S111: Divide the microservice into different microservice modes according to the integration mode to which the microservice belongs or the calling protocol used.

Among them, the integration mode of microservices can be divided into aggregator microservice design mode, agent microservice design mode, chain microservice design mode, branch microservice design mode, data sharing microservice design mode, and asynchronous messaging microservice related mode. According to different integration modes, the microservice mode can be divided into the above 6 types, but the above integration mode is not limited here.

The calling protocol of microservices can include the following 5 types, but is not limited to the following 5 types:

1. According to the semantics targeted by the agreement, it is divided into:

Resource-oriented: REST;

Command-oriented: SOAP, RMI, RPC;

Event-oriented: XMPP, JMS, AMQP;

2. According to the coding of the remote call protocol, it can be divided into:

Text protocol: HTTP+JSON/XML, SIP;

Binary protocol: WebSocket+BSon/Protobuf;

3. According to the purpose of the agreement, it can be divided into:

Signaling and control protocols: SIP, SDP, Jingle, ROAP;

Media transmission protocol: HTTP, RTP, RTMP;

Security related protocols: TLS, DTLS, oAuth2;

4. Divided into according to the interactive mode:

Request/response

Request/receive;

Request/negotiation/confirmation;

Publish/subscribe;

5. According to the data transmission format, it is divided into:

Text format: key-value pairs, Json, Xml;

Binary format: Proto buffer, BSON, Thrift, PDU.

In this implementation, the microservices of the IT system are divided into different microservice modes according to different integration modes or calling protocols, which provides the possibility for subsequent uniform coding of services. Different integration modes or calling protocols correspond to different registration centers. First, the IT system's services are divided into different microservice modes according to different integration modes or invocation protocols, which is to divide similar registries in each microservice together to become a registrar under the same microservice mode.

Referring to Fig. 8, Fig. 8 is a second embodiment of the unified management method for microservices with multiple registries under this application. The unified management method for microservices with multiple registries includes the following steps:

Step S210: Divide the microservices into different microservice modes according to preset conditions.

Step S220: According to the change of the service status of the microservice, a service discovery mechanism is dynamically triggered to obtain the service information of the different microservice modes.

Step S230: The service information of the different microservice modes is converted into a service code of a unified format through a preset unified coding rule, and stored in the service registry.

Step S240: Perform intelligent analysis on the service code in the unified format to match the corresponding microservice, and encapsulate it into a corresponding application program interface.

Step S250: Perform multi-dimensional management on the encapsulated corresponding application program interface; wherein, the multi-dimensional management includes at least one of the following: state management of microservices, request current limiting, and fusing.

Compared with the first embodiment, the second embodiment includes step S250. The other steps are the same as those in the first embodiment, and will not be repeated here.

State management of microservices is to manage the running status of service instances of microservices. If the agent finds a problem with the service instance, it can take corrective measures, such as shutting down the failed instance or starting another service instance.

Request flow limiting is used to selectively limit certain requests for traffic exceeding expectations through preset flow limiting rules and flow limiting algorithms.

Fuse is to turn off the current path in a specific scenario, so as to protect the entire system.

This is not limited to the above-mentioned multi-dimensional management, and may also be other microservice management.

The beneficial effect in the above-mentioned embodiment: the program interface corresponding to the package can not only be consumed by the consumer, but also can be managed in multiple dimensions, including the state management of microservices, request current limiting or fuse, so that the unified management of this application The method has greater applicability.

The application also provides a device, which is characterized in that it comprises:

The division module is used to divide microservices into different microservice modes according to preset conditions;

The service information acquisition module is configured to dynamically trigger a service discovery mechanism according to the change of the service status of the microservice to acquire the service information of the different microservice modes;

The unified coding module is used to convert the service information of the different microservice modes into a unified format service code through preset unified coding rules, and store it in the service registry;

The application module is used for intelligently analyzing and matching the corresponding microservices on the service code in the unified format, and encapsulating it into a corresponding application program interface for consumption by the consumer.

The device shown in Fig. 9 includes a division module 21, a service information acquisition module 22, a unified coding module 23, and an application module 24. The device can execute the methods of the embodiments shown in Figs. 2 to 8, and the parts not described in detail in this embodiment are Reference may be made to the related descriptions of the embodiments shown in FIG. 2 to FIG. 8. For the implementation process and technical effects of this technical solution, please refer to the description in the embodiment shown in FIG. 2 to FIG. 8, which will not be repeated here.

The present application also provides a computer-readable storage medium. The computer-readable storage medium may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on the computer, the computer executes the following steps:

Divide microservices into different microservice modes according to preset conditions; dynamically trigger a service discovery mechanism according to changes in the service status of the microservices to obtain service information of the different microservice modes; divide the different microservices The service information of the service mode is converted into a unified format service code through preset unified coding rules, and stored in the service registry; the unified format service code is intelligently analyzed to match the corresponding microservice, and packaged into a corresponding application The program interface is for the consumer to consume.

The present application also provides a device including a memory, a processor, and a program of a method for unified management of microservices of multiple registries stored in the memory and running on the processor, and the processor executes the microservices of the multiple registries. The program of the unified service management method implements any of the above-mentioned methods.

Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

This application is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of this application. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

It should be noted that in the claims, any reference signs located between parentheses should not be constructed as limitations on the claims. The word "comprising" does not exclude the presence of parts or steps not listed in the claims. The word "a" or "an" preceding a component does not exclude the presence of multiple such components. The application can be realized by means of hardware including several different components and by means of a suitably programmed computer. In the unit claims listing several devices, several of these devices may be embodied in the same hardware item. The use of the words first, second, and third, etc. do not indicate any order. These words can be interpreted as names.

Although the preferred embodiments of the present application have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

Obviously, those skilled in the art can make various changes and modifications to this application without departing from the present invention.

Ming’s spirit and scope. In this way, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, then this application is also intended to include these modifications and variations.

Claims

A method for unified management of microservices with multiple registries. The method for unified management of microservices with multiple registries includes:

Divide microservices into different microservice modes according to preset conditions;

According to the change of the service status of the microservice, dynamically trigger a service discovery mechanism to obtain the service information of the different microservice modes;

The service information of the different microservice modes is converted into a service code of a unified format through preset unified coding rules, and stored in the service registry;

The service code in the unified format is intelligently analyzed and matched to the corresponding microservice, and encapsulated into a corresponding application program interface for consumption by the consumer.
The method for unified management of microservices with multiple registration centers according to claim 1, wherein the service information is an attribute corresponding to a service instance in each registration center, and the attribute includes at least one of the following: Internet Protocol address, port number , Whether it is a temporary service instance, the weight used to select the optimal service instance call, health status and metadata.
The method for unified management of microservices with multiple registries according to claim 2, characterized in that said converting the service information of the different microservice modes into service codes of a unified format through a preset unified coding rule comprises:

Selecting attributes applied to the unified coding rule;

Preset the number of coding bits corresponding to each attribute selected;

The selected attributes are concatenated in a preset order to obtain the service code in the unified format.
The method for unified management of microservices with multiple registries according to claim 3, wherein said converting the service information of the different microservice modes into service codes in a unified format through preset unified coding rules, further comprises:

When the attribute selected in the uniform coding rule is missing in the service information, a zero-padded operation is performed on the missing attribute.
The method for unified management of microservices with multiple registration centers according to claim 3, wherein the intelligent analysis of the service code in the unified format comprises:

Obtaining the uniform format service code corresponding to the service name from the service registration table in real time;

According to the coding digits corresponding to each attribute, the corresponding attributes are sequentially obtained.
The method for unified management of microservices with multiple registries according to claim 3, wherein the selection of the attributes applied to the unified coding rule includes:

The full set of attributes corresponding to each service instance is selected to be applied to the unified coding rule.
The method for unified management of microservices with multiple registries according to claim 1, wherein said dividing microservices into different microservice modes according to preset conditions comprises:

According to the integration mode to which the microservice belongs or the calling protocol used, the microservice is divided into different microservice modes.
A unified management device for microservices with multiple registration centers, including a memory, a processor, and computer-readable instructions stored in the memory and running on the processor, and the processor executes the computer-readable instructions When implementing the following steps:

Divide microservices into different microservice modes according to preset conditions;

According to the change of the service status of the microservice, dynamically trigger a service discovery mechanism to obtain the service information of the different microservice modes;

The service information of the different microservice modes is converted into a service code of a unified format through preset unified coding rules, and stored in the service registry;

The service code in the unified format is intelligently analyzed and matched to the corresponding microservice, and encapsulated into a corresponding application program interface for consumption by the consumer.
The device for unified management of microservices with multiple registration centers according to claim 8, wherein when the processor executes the computer-readable instructions to realize that the service information is the attribute corresponding to the service instance in each registration center, the The attributes include at least one of the following:

Internet protocol address, port number, whether it is a temporary service instance, the weight used to select the optimal service instance call, health status, and metadata.
The device for unified management of microservices with multiple registration centers according to claim 9, wherein the processor executes the computer-readable instructions to implement the process of passing the service information of the different microservice modes through a preset unified coding rule When converting to a uniform format service code, the following steps are included:

Selecting attributes applied to the unified coding rule;

Preset the number of coding bits corresponding to each attribute selected;

The selected attributes are concatenated in a preset order to obtain the service code in the unified format.
The device for unified management of microservices with multiple registration centers according to claim 10, wherein the processor executes the computer-readable instructions to implement the process of passing the service information of the different microservice modes through a preset unified coding rule When converting to a uniform format service code, the following steps are also included:

When the attribute selected in the uniform coding rule is missing in the service information, a zero-padded operation is performed on the missing attribute.
10. The device for unified management of microservices with multiple registration centers according to claim 10, wherein when the processor executes the computer-readable instructions to realize the intelligent analysis of the service code in the unified format, the method comprises the following steps:

Obtaining the uniform format service code corresponding to the service name from the service registration table in real time;

According to the coding digits corresponding to each attribute, the corresponding attributes are sequentially obtained.
The device for unified management of microservices with multiple registration centers according to claim 10, wherein, when the processor executes the computer-readable instructions to implement the selection of the attributes applied to the unified coding rule, the method comprises the following steps:

The full set of attributes corresponding to each service instance is selected to be applied to the unified coding rule.
The device for unified management of microservices with multiple registration centers according to claim 8, when the processor executes the computer-readable instructions to realize the division of microservices into different microservice modes according to preset conditions, comprising the following steps :

According to the integration mode to which the microservice belongs or the calling protocol used, the microservice is divided into different microservice modes.
A computer-readable storage medium in which computer instructions are stored, and when the computer instructions are executed on a computer, the computer executes the following steps:

Divide microservices into different microservice modes according to preset conditions;

According to the change of the service status of the microservice, dynamically trigger a service discovery mechanism to obtain the service information of the different microservice modes;

The service information of the different microservice modes is converted into a service code of a unified format through preset unified coding rules, and stored in the service registry;

The service code in the unified format is intelligently analyzed and matched to the corresponding microservice, and encapsulated into a corresponding application program interface for consumption by the consumer.
The computer-readable storage medium according to claim 15, when the computer instructions are executed on the computer, the computer is caused to further execute the following steps:

The service information is an attribute corresponding to the service instance in each registry, and the attribute includes at least one of the following: Internet Protocol address, port number, whether it is a temporary service instance, the weight used to select the optimal service instance call, and health Status and metadata.
The computer-readable storage medium according to claim 16, when the computer instructions are executed on the computer, the computer is caused to further perform the following steps:

Selecting attributes applied to the unified coding rule;

Preset the number of coding bits corresponding to each attribute selected;

The selected attributes are concatenated in a preset order to obtain the service code in the unified format.
The computer-readable storage medium according to claim 17, when the computer instructions are executed on the computer, the computer is caused to further perform the following steps:

When the attribute selected in the uniform coding rule is missing in the service information, a zero-padded operation is performed on the missing attribute.
The computer-readable storage medium according to claim 17, when the computer instructions are executed on the computer, the computer is caused to further perform the following steps:

Obtaining the uniform format service code corresponding to the service name from the service registration table in real time;

According to the coding digits corresponding to each attribute, the corresponding attributes are sequentially obtained.
A unified management device for microservices with multiple registration centers. The unified management device for microservices with multiple registration centers includes:

The division module is used to divide microservices into different microservice modes according to preset conditions;

The service information acquisition module is used to dynamically trigger the service discovery mechanism according to the change of the service status of the microservice to acquire the service information of the different microservice modes;

The unified coding module is used to convert the service information of the different microservice modes into a unified format service code through preset unified coding rules, and store it in the service registry;

The application module is used for intelligently analyzing and matching the corresponding microservices on the service code in the unified format, and encapsulating it into a corresponding application program interface for consumption by the consumer.