CN106603582B - Network micro-service discovery method - Google Patents

Abstract

The invention discloses a method for discovering micro-services in a network, comprising: a service provider broadcasts an XML micro-service description file to a network according to a service registration center specification; a service requester broadcasts an XML micro-service requirement description file to the network according to the service registration center specification; XML The requirement description file is automatically matched with the functional/non-functional/data content in the XML service description file; the successfully matched microservices start routing, and perform service caching at the executable network nodes they pass through. Through the present invention, the service provider can publish micro-services to the network at any time, and actively register with the service registration center; the service requester can search for the required micro-services in the network in three ways: automatic, semi-automatic and hosting, which greatly improves Improved usability of microservices.

Description

A network microservice discovery method

technical field

The invention belongs to the technical field of information networks, in particular to a method for discovering network microservices.

Background technique

With the rapid development of Internet technology and applications and the rapid growth of Internet users, the complexity and diversification of content services has become the main theme of Internet development. The traditional monolithic system is gradually unable to cope with the massive content-filled Internet and the huge enterprise informatization environment, especially in the massive heterogeneous data transmission, quality assurance and tens of millions of different service interconnection requirements and the software industry can provide. The paradox of computing, storage and transmission capabilities.

In response to the above challenges, countries have carried out research on new software, network systems and key technologies. As an extension of service-oriented thinking, microservice architecture can solve the above problems to a certain extent, including the flexibility of software implementation, the adaptability of software services, and the scalability of network transmission. The microservice architecture can develop and assemble a single application as an independent suite composed of many small services, thereby providing a large-scale application system with quality assurance and flexible functions, in which each service has its own process and adopts lightweight Mechanisms for communication between services. The micro-service architecture is built around business functions, and independent deployment and completion of independent business functions are realized by the automatic deployment mechanism, which is convenient to assemble into large-scale business implementations at any time and match the minimum central management mechanism. Different services are not restricted by the development language and operating environment .

However, due to its flexibility and strong scalability, microservices also lead to the query and invocation of massive microservices in the network environment in terms of granular design, service scheduling, and service composition. In order to solve the related problems, the present invention proposes a network microservice. Service discovery method.

SUMMARY OF THE INVENTION

The purpose of the present invention is to propose a network microservice discovery method in order to solve the query and invocation problem of massive microservices in the network environment, which achieves the mutual identification problem between microservices through interconnection and centralized management, and improves network performance. Ease of use in microservices.

For achieving the above object, the present invention adopts the following technical scheme:

A network microservice discovery method includes the following steps:

Step 101, the service provider broadcasts the XML micro-service description file to the network according to the service registration center specification;

Step 102, the service requester broadcasts the XML microservice requirement description file to the network according to the service registration center specification;

Step 103, the XML requirement description file automatically matches the function/non-function/data content in the XML service description file;

Step 104 , the successfully matched microservices start routing, and perform service caching on the passing executable network nodes.

Preferably, the microservice description specification based on XML format includes:

For service providers: the description needs to include the provided microservice function information, service provider information, microservice application information, microservice deployment information, microservice performance information, and microservice QOS information;

For the service registry: it needs to describe the invocation information of the service, the evaluation information of the microservice, the authentication information of the microservice, and the security information of the microservice;

For the service requester: it needs to describe the demand function information of the microservice, the demand call information of the microservice, the usage information of the microservice, and the evaluation information of the user.

Preferably, in step 103, when the node that can parse the XML service requirement file obtains the service requirement information, it starts to match the content of the XML file with its own XML microservice description file, not only through service registration. Calculate the match and point to it by IP, and return the microservice link information to the service requester after the match is successful;

Preferably, in step 104, the network node that satisfies the service registry specification in the process of routing the micro-service information will identify the micro-service XML file and detect whether the micro-service can be executed, and if the micro-service can be executed, the network node will cache the micro-service ; The computing and data capabilities of microservices are routed through matching content, not just pointing or scheduling through the service registry.

The invention provides a method for discovering micro-services in a network. The method comprises the following steps: a service providing service registration center broadcasts an XML micro-service description file to a network according to a specification; a service requester broadcasts an XML micro-service to the network according to the service registration center specification. Requirement description file; the XML requirement description file is automatically matched with the functional/non-functional/data content in the XML service description file; the successfully matched microservices start routing, and perform service caching at the executable network nodes they pass through. Through the present invention, the service provider can publish micro-services to the network at any time, and actively register with the service registration center; the service requester can search for the required micro-services in the network in three ways: automatic, semi-automatic and hosting, which greatly improves Improved usability of microservices.

Description of drawings

1 shows a flowchart of a method for discovering network microservices according to an embodiment of the present invention;

2 shows a structural diagram of a method for discovering network microservices according to an embodiment of the present invention;

FIG. 3 shows a flowchart of a service discovery process of a network microservice discovery method according to an embodiment of the present invention.

Detailed ways

The following is a detailed description of the embodiments of the present invention, which are labeled in the accompanying drawings, and the same or similar reference numerals are used throughout the drawings to denote the same or similar components or components having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary, and are only used to explain the present invention, but not to be construed as a limitation of the present invention.

It will be understood by those skilled in the art that the singular forms "a", "an", "the" and "the" as used herein can include the plural forms as well, unless expressly stated otherwise. It should be further understood that the word "comprising" used in the description of the present invention refers to the presence of stated features, integers, steps, operations, elements and/or components, but does not exclude the presence or addition of one or more other features, Integers, steps, operations, elements, components and/or groups thereof. It will be understood that when we refer to an element as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Furthermore, "connected" or "coupled" as used herein may include wirelessly connected or "coupled." As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It should also be understood that terms such as those defined in general dictionaries should be understood to have meanings consistent with their meanings in the context of the prior art and, unless defined as herein, are not to be taken in an idealized or overly formal sense. explain.

As shown in Figure 1, the present invention provides a method for discovering network microservices, comprising the following steps:

101. The service provider encapsulates the produced microservice function content, data content, QOS content and other information into an XML microservice description file according to the specifications of the service registry and publishes it to the network;

102, the service requester encapsulates the required microservice functional requirements, performance requirements, security requirements and other information into an XML service requirement file according to the specifications of the service registry and publishes it to the network;

103. When the node capable of parsing the XML service requirement file obtains the service requirement information, it starts to match the content of the XML file with its own XML microservice description file, and returns the microservice link information to the service requester after the matching is successful;

104 , the network node that satisfies the service registry specification during the microservice information routing process will identify the microservice XML file and detect whether the microservice can be executed, and if the microservice can be executed, the network node will cache the microservice.

In step 101:

The service provider needs to describe, including but not limited to, the provided microservice function information, service provider information, microservice application information, microservice deployment information, microservice performance information, and microservice QOS information, etc.;

Microservices include but are not limited to service installation files, service operating environment and service data;

The installation files, service operating environment and service data of microservices can be separated and support remote calls;

The development language, operating environment and service data of microservices include but are not limited to the current mainstream development language, operating environment and database or other data storage forms.

In step 102:

The service requester needs to describe but not limited to the demand function information of the microservice, the demand call information of the microservice, the usage information of the microservice, and the evaluation information of the user, etc.

A service requester can request a microservice in two ways. One is to search for and invoke the service in the service registry, and the other is to directly publish the microservice request and communicate with the service provider to use the microservice.

In step 103:

The service requester and the service provider match the content in the XML service requirement file and the XML service description file through the XML service requirement file published by them, not only through the calculation and matching in the service registration and pointing through the IP.

In step 104:

The computing and data capabilities of microservices are routed through matching content, not just pointing or scheduling through the service registry;

During the routing process, the microservice will perform service executable environment detection on the passing nodes. After the detection is successful, the microservice will be cached in different nodes.

In steps 101 to 103:

The service registration center formulates the service description specification in the network, but does not actively intervene in the service routing process. At the same time, the service registration center needs to describe but not limited to service invocation information, microservice evaluation information, microservice authentication information, and microservice security. information, etc.;

Service registry, service provider and service requester follow the same microservice description specification based on XML format;

The service provider broadcasts the XML service description file in the network according to the specification, or actively sends the XML service description file to the service registration center;

The service registry will automatically grab the XML service description file that conforms to the specification in the network;

The service registry automatically parses the XML service description file, detects the corresponding microservices according to the file description, and modifies the service description XML file for rating and certification;

The service requester publishes the microservice request in the network and publishes the XML service requirement file that follows the specification, or can call the service registry of the service to search for the required XML service description file, or obtain the required microservice XML in the network according to the specification. service description file.

FIG. 2 is a structural diagram of a microservice discovery method according to an embodiment of the present invention. Among them, the service registry is used to formulate the microservice description specification. The service requester and service provider need to compile and publish the XML service requirement file and the XML microservice description file according to the service specification; in principle, the service registry does not interfere with the microservice. However, the service requester can also directly retrieve the service through the service registry; the service registry will capture the relevant service usage information of the service requester and service provider, and describe it in the microservice description XML file as needed. Edit some information; the XML file published by the service requester is matched with the XML file provided by the service provider according to the rules provided by the service registry. The matching includes but is not limited to functional content, performance content, data structure, security, QOS indicators, etc. The XML requirement description file will match multiple XML service description files and return the microservice to the service requester. After the connection is successful, the microservice will be routed; during the microservice routing process, the microservice will pass through identifiable and executable network nodes. cache.

FIG. 3 is a flowchart of a service discovery process of a network microservice discovery method according to an embodiment of the present invention. First, the service requester compiles the XML service requirement file according to the rules of the registration center, and the service requester publishes the service requirement XML description to the whole network, which includes the service functionality, non-functionality, data structure, and operating environment of the service requester. and other requirements; the service provider compiles the microservice XML description file according to the rules of the service registry, which includes the service provider's microservice description, non-functional description, QOS description, security description, etc.; The node of the registry rule will identify the received service requirement XML description file, parse it, and match it with its own microservice XML service description file. If the match is successful, it will return a success message to the service requester and provide the corresponding microservice; In the process of routing to the service requester, the microservice will identify the microservice XML description file of the passing node. If it finds that the operating environment can support backup, it will cache and run a copy of the node; the service registry will collect the data in the network. The service requester's service requirement XML file and the service provider's microservice XML description file. At the same time, the service registry can complete two functions. One is to act as a centralized controller. When the service requester actively sends service requirements to the service registry Specify a microservice provider for it, and the second is to evaluate the service quality of the microservice and modify the content of the corresponding part of the XML microservice description file.

The technical solution proposed by the present invention solves the query and invocation problem of massive micro-services in the network environment, and proposes a network micro-service discovery method, which achieves mutual identification, routing, The cache problem improves the usability of microservices in the network.

As will be appreciated by those skilled in the art, the present invention may relate to apparatus for performing one or more of the operations described in this application. The apparatus may be specially designed and manufactured for the required purposes, or it may comprise known apparatuses in a general-purpose computer selectively activated or reconfigured with a program stored therein.

Those skilled in the art will understand that computer program instructions can be used to implement each block of these structural diagrams and/or block diagrams and/or flow diagrams, and combinations of blocks in these structural diagrams and/or block diagrams and/or flow diagrams . These computer program instructions may be provided to a processor of a general purpose computer, specialized computer or other programmable data processing method to create a machine whereby the instructions executed by the processor of the computer or other programmable data processing method create a structure for implementing A method specified in a block or blocks of a diagram and/or block diagram and/or flow diagram.

Those skilled in the art can understand that the various operations, methods, steps, measures, and solutions discussed in the present invention may be alternated, modified, combined or deleted. Further, other steps, measures, and solutions in the various operations, methods, and processes that have been discussed in the present invention may also be alternated, modified, rearranged, decomposed, combined, or deleted. Further, steps, measures and solutions in the prior art with various operations, methods, and processes disclosed in the present invention may also be alternated, modified, rearranged, decomposed, combined or deleted.

The above are only some embodiments of the present invention. It should be pointed out that for those skilled in the art, without departing from the principles of the present invention, several improvements and modifications can be made. It should be regarded as the protection scope of the present invention.

Claims (3)

1. a network microservice discovery method, is characterized in that, comprises the following steps: Step 101, the service provider broadcasts the XML micro-service description file to the network according to the service registration center specification; Step 102, the service requester broadcasts the XML microservice requirement description file to the network according to the service registration center specification; Step 103, the XML requirement description file automatically matches the function/non-function/data content in the XML service description file; Step 104, the successfully matched microservices start routing, and perform service caching on the passing executable network nodes; Wherein, in step 104, the network node that satisfies the service registry specification during the routing of the micro-service information will identify the micro-service XML file and detect whether the micro-service can be executed, and if it can be executed, the micro-service is cached at the network node; The computing and data capabilities of microservices are routed through matching content, not just pointing or scheduling through the service registry. 2. method according to claim 1, is characterized in that: For service providers: the description needs to include the provided microservice function information, service provider information, microservice application information, microservice deployment information, microservice performance information, and microservice QOS information; For the service registry: it needs to describe the invocation information of the service, the evaluation information of the microservice, the authentication information of the microservice, and the security information of the microservice; For the service requester: it needs to describe the demand function information of the microservice, the demand call information of the microservice, the usage information of the microservice, and the evaluation information of the user. 3. The method for discovering network microservices according to claim 1, wherein in step 103, when a node capable of parsing the XML service requirement file obtains the service requirement information, it begins to describe the content of the XML file and its own XML microservice The file is matched on the content, not only through the calculation and matching in the service registration and pointing through the IP. After the matching is successful, the microservice link information is returned to the service requester.

Images