WO2022193979A1

WO2022193979A1 - Microservice development method and system, and computer device and medium

Info

Publication number: WO2022193979A1
Application number: PCT/CN2022/079551
Authority: WO
Inventors: 施瑜; 刘源
Original assignee: 易保网络技术(上海)有限公司
Priority date: 2021-03-16
Filing date: 2022-03-07
Publication date: 2022-09-22
Also published as: CN115086412A

Abstract

The present invention relates to a microservice development method and system, and an associated computer device and a medium. In particular, the present invention provides a microservice development method applied to a development microservice node, and is characterized in that the method comprises: deploying a running instance of a microservice; registering an IP address of the development microservice node and a microservice name of the deployed microservice with a microservice registration server; and initiating a test on the running instance of the microservice.

Description

A microservice development method, system, and computer equipment and medium

technical field

The present invention relates to the field of computer technology, and in particular, to a microservice development method, system, and associated computer equipment and medium.

Background technique

With the rapid development of information technology, the application software architecture has undergone tremendous changes, and the traditional monolithic architecture has been transformed into a new type of microservice architecture.

Microservice architecture is a new technology for deploying applications and services in the cloud. Microservices are split from the original single business system into multiple small applications that can be independently developed, involved, operated and maintained. Microservices is an architectural style, for example, an application needs to be composed of at least one microservice. Each microservice in the system can be deployed independently, and each microservice is loosely coupled. Each microservice, as a small application, is only focused on accomplishing one task and doing it well. Moreover, when technicians upgrade a microservice, they often test the microservice to ensure that the updated microservice can be used normally with other microservices in the software application.

However, in the prior art, when developing microservices, it is necessary to build a development environment for the overall microservice link. Due to the strong calling relationship between each microservice, it is necessary to deploy a full amount of microservices to the development environment. This will lead to the following problems: it takes a long time to build a microservice development environment, such as it usually takes many days to build; and the development environment is difficult to debug, such as spending a lot of time in the testing process to determine whether it is a test environment problem; at the same time, the development environment is unstable, For example, the test is often blocked due to a problem with a microservice.

Therefore, a new microservice development method, system, and computer equipment and medium are needed to develop microservices efficiently.

SUMMARY OF THE INVENTION

According to one aspect of the present invention, a microservice development method applied to the development of microservice nodes is provided, wherein the method includes: deploying a running instance of the microservice; converting the IP address of the development microservice node and the The microservice name of the deployed microservice is registered with the microservice registration server; and the test of the running instance of the microservice is initiated.

Further, according to an aspect of the present invention, the IP address of the development microservice node is associated with the microservice name of the microservice on the microservice registration server.

Further, in an aspect according to the present invention, the running instance of the microservice is privately accessed.

Further, according to an aspect of the present invention, when a test of the running instance of the microservice is initiated, the development microservice node invokes the running instance of the microservice deployed on the public microservice node.

Further, according to an aspect of the present invention, invoking the running instance of the microservice deployed on the public microservice node includes: the development microservice node querying the microservice registration server for the microservice called by the test the microservice name.

Further, according to an aspect of the present invention, the development microservice node obtains an IP address associated with the microservice name from the microservice registration server, wherein the IP address includes the public microservice node IP address.

Further, according to an aspect of the present invention, the development microservice node selects the IP address of the public microservice node for testing, so as to invoke the running instance of the microservice deployed on the public microservice node.

Further, according to an aspect of the present invention, when the IP address also includes the IP address of the development microservice node, the development microservice node preferentially selects the IP address of the development microservice node to call the microservice. Run the example to test.

Further, in an aspect according to the present invention, the development microservice node is a computing node composed of one or more entity computers.

Further, according to one aspect of the present invention, the method runs under the Spring Cloud microservice framework.

According to another aspect of the present invention, a microservice development method applied to a public microservice node is provided, wherein the method includes: deploying a running instance of the microservice, wherein the running instance of the microservice keeps run for other nodes to test; register the IP address of the public microservice node and the microservice name of the deployed microservice with the microservice registration server.

Further, according to another aspect of the present invention, the IP address of the public microservice node is associated with the microservice name of the microservice on the microservice registration server.

Further, in yet another aspect according to the present invention, the running instance of the microservice is publicly accessible.

Further, according to another aspect of the present invention, the public microservice node obtains the IP address associated with the microservice name from the microservice registration server.

Further, according to another aspect of the present invention, the public microservice node selects the obtained IP address to invoke the running instance of the microservice deployed on other nodes.

Further, in another aspect according to the present invention, the public microservice node is a computing node composed of one or more entity computers.

Further, in another aspect according to the present invention, the method runs under the Spring Cloud microservice framework.

According to still another aspect of the present invention, a micro-service development system for developing micro-service nodes is provided, wherein the system includes: a deployment module, the deployment module deploys a running instance of the micro-service; a registration module , the registration module registers the IP address of the development microservice node and the microservice name of the deployed microservice to the microservice registration server; and a test module, which initiates the operation of the microservice instance test.

Further, in still another aspect of the present invention, the IP address of the development microservice node is associated with the microservice name of the microservice on the microservice registration server.

Further, in still another aspect according to the present invention, the running instance of the microservice is accessed privately.

Further, according to still another aspect of the present invention, when the test module initiates the test on the running instance of the microservice, the test module invokes the test module of the microservice deployed on the public microservice node. Run the instance.

Further, according to still another aspect of the present invention, the test module invoking the running instance of the microservice deployed on the public microservice node includes: the registration module queries the microservice registration server for the test service The microservice name of the called microservice.

Further, according to still another aspect of the present invention, the microservice development system obtains the IP address associated with the microservice name, wherein the IP address includes the IP address of the public microservice node.

Further, according to still another aspect of the present invention, the test module selects the IP address of the public microservice node for testing, so as to invoke the running instance of the microservice deployed on the public microservice node.

Further, according to still another aspect of the present invention, when the IP address also includes the IP address of the development microservice node, the test module preferentially selects the IP address of the development microservice node to call the microservice. Run the example to test.

Further, in still another aspect of the present invention, the development microservice node is a computing node composed of one or more entity computers.

Further, in still another aspect according to the present invention, the system runs under the Spring Cloud microservice framework.

According to another aspect of the present invention, a microservice development system applied to a public microservice node is provided, wherein the system includes: a deployment module, the deployment module deploys a running instance of the microservice, wherein the The running instance of the microservice keeps running for other nodes to test; the registration module registers the IP address of the public microservice node and the microservice name of the deployed microservice with the microservice registration server.

Further, in another aspect according to the present invention, the running instance of the microservice is publicly accessible.

Further, according to another aspect of the present invention, the system obtains the IP address associated with the microservice name from the microservice registration server.

Further, according to another aspect of the present invention, the system further includes a calling module, the calling module selects the obtained IP address to call the running instance of the microservice deployed on other nodes.

Further, according to another aspect of the present invention, the public microservice node is a computing node composed of one or more entity computers.

Further, according to another aspect of the present invention, the system runs under the Spring Cloud microservice framework.

According to yet another aspect of the present invention, there is provided a computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing a computer program according to the present invention when the processor executes the program The steps of the method of the aspect.

According to still another aspect of the present invention, there is provided a recording medium having stored thereon a computer program executed by a computer to implement the steps of the method according to an aspect of the present invention.

According to one or more embodiments of the present invention, single or multiple microservice nodes can be developed and debugged without simultaneously starting the entire microservice link or other microservice nodes unrelated to the single or multiple microservice nodes;

According to one or more embodiments of the present invention, a microservice node can implement routing selection by calling other microservice nodes or development nodes, thereby saving microservice node resources.

Description of drawings

Figure 1 shows a schematic diagram 100 of microservice development according to one embodiment of the present invention.

FIG. 2 shows a schematic diagram 200 of microservice development according to another embodiment of the present invention.

FIG. 3 shows a microservice development method 300 applied to develop a microservice node according to an embodiment of the present invention.

FIG. 4 shows a microservice development method 400 applied to a public microservice node according to an embodiment of the present invention.

FIG. 5 shows a microservice development system 500 applied to develop a microservice node according to an embodiment of the present invention.

FIG. 6 shows a microservice development system 600 applied to a public microservice node according to an embodiment of the present invention.

7 is an example block diagram 700 of a computer device for the methods described herein, according to one embodiment of the present invention.

Detailed ways

The data encryption and decryption method, device and computer medium involved in the present invention will be further described in detail below with reference to the accompanying drawings. It should be noted that the following specific embodiments are exemplary rather than limiting, and are intended to provide a basic understanding of the present invention, and are not intended to identify key or critical elements of the present invention or limit the scope of protection to be protected.

The present invention is described below with reference to block illustrations, block diagrams, and/or flow diagrams of methods and apparatuses of embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer or other programmable data processing device to constitute a machine so that execution of the instructions by the processor of the computer or other programmable data processing device creates a process for carrying out the processes Elements of the functions/operations specified in the figures and/or blocks and/or one or more flowchart diagrams.

These computer program instructions may be stored in a computer readable memory, the instructions may instruct a computer or other programmable processor to perform functions in a particular manner, such that the instructions stored in the computer readable memory constitute the flowcharts and/or A manufactured product of the instruction components for the function/operation specified in one or more of the blocks of the block diagram.

These computer program instructions can be loaded on a computer or other programmable data processor to cause a series of operational steps to be performed on the computer or other programmable processor to constitute a computer-implemented process for causing the computer or other programmable data The instructions executing on the processor provide steps for implementing the functions or operations specified in one or more blocks of this flowchart and/or block diagram. It should also be noted that in some alternative implementations, the functions/operations noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality/operations involved.

As described in the background art, in the existing development of microservices, it is necessary to deploy all microservices on test nodes or develop unit tests for all microservices to complete the development involving multiple microservices. However, the development method in the conventional method brings huge resource consumption and is difficult to debug. To solve this problem, the present disclosure proposes a microservice development method, system, and computer device and medium. The method, device and computer medium involved in the present invention can be used for micro-service development between public micro-service nodes, micro-service registration servers and development micro-service nodes in a micro-service link. Nodes implement a limited number of microservice startups, and can be dev-tested against a single or several microservices.

Figure 1 shows a schematic diagram 100 of microservice development according to one embodiment of the present invention. As shown in FIG. 1 , the microservice development method according to the present invention may include three parties, namely a public microservice node 101 , a microservice registration server 102 and a development microservice node 103 . As can be understood by those skilled in the art, in the present invention, the node server is not necessarily a single entity computer, but may be a computing node composed of one or more computers, servers or computing devices. All or part of the running instance of the microservice can be run on the computing node. The public microservice node 101 is a public node on which multiple running instances of the microservices 110, 120 to N are deployed (depending on the computing capability of the public microservice node). The running instance of the microservice running on the public microservice node 101 is public and can be invoked by any remote node. In contrast, the development microservice node 103 is a private node on which a running instance of the microservice 110 runs, and the running instance can only be accessed and debugged by the developer. The microservice registration server is a public service registration server, on which the IP address of the microservice node and the microservice name of the microservice deployed on the microservice node can be registered, and the IP address of the microservice node can be deployed on the server. The microservice name associated with the microservice. Correspondingly, the microservice registration server can also obtain the IP address of the associated microservice node by parsing the microservice name of the microservice.

As described above, in the prior art, when a private node performs microservice debugging, all associated microservices need to be deployed on the private node, that is, the development microservice node 103 . This increases the computation of private nodes and is not suitable for modern iterative software development.

The present disclosure provides a brand-new microservice development method. Methods can run under the Spring Cloud microservices framework. As shown in FIG. 1 , the development microservice node 103 deploys only the running instance of the microservice 110 , while the public microservice node 101 may deploy multiple running instances of the microservice 120 to N depending on its computing capability. At the beginning of the method, the public microservice node 101 and the development microservice node 103 respectively register their IP addresses and the microservice name of the deployed microservice with the microservice registration server. When the running instance of the microservice is started, the microservice name of the microservice and the IP address of the node where the microservice is deployed will be registered on the microservice registration server and associated as a mapping relationship. In other words, on the microservice registration server, the IP address of the node and the microservice name of the microservice deployed on the node are associated. The node can obtain the address of the node where the microservice associated with the microservice name is deployed by querying the microservice name. The specific method will be introduced below.

The development microservice node 103 may begin testing the running instance of the microservice 110 . By way of example, testing of a running instance of microservice 110 may involve invoking a running instance of microservice 120 . In this case, the development microservice node 103 will query the microservice registration server 102 for the microservice name of the microservice 120. The microservice registration server 102 parses the microservice name of the microservice 120 and finds the IP address associated with the microservice name on the microservice registration server 102, ie, the IP address of the public microservice node. The development microservice node will periodically obtain the IP address of the node associated with the microservice name from the microservice registration server 102 . The development microservice node 103 selects the obtained IP address of the public microservice node to call the running instance of the microservice 120 on the public microservice node 101 for testing, thereby avoiding deploying the running instance of the microservice 120 to the local development microservice node work. In addition, remotely calling the running instance of the microservice on the public microservice development node can realize the joint development and invocation of the microservice by multiple private development microservice nodes. In parallel, the utilization efficiency of running instances of microservices is improved.

In addition, the public microservice node 103 can also call the running instance of the microservice on the development microservice node 101 when necessary. By way of example, when the development microservice node 101 invokes the running instance of the microservice 120 of the public microservice node 103 , the running instance of the microservice 120 may need information of the running instance of the microservice 110 . Therefore, the public microservice node 103 will query the microservice name of the microservice 110 on the microservice registration server 102 . The public microservice node 103 obtains the IP address associated with the microservice name of the microservice 110 from the microservice registration server 102 , that is, the IP address of the development microservice node 101 . . The public microservice node 103 selects the IP address to call the running instance of the microservice 110 deployed on the development microservice node, so as to satisfy the development microservice node 101's call to the running instance of the microservice 120 on the public microservice node 103. This implementation develops the testing of the microservice by the microservice node.

FIG. 2 shows a schematic diagram 200 of microservice development according to another embodiment of the present invention. The microservice development method described in FIG. 2 can further realize the optimal routing of the microservice by the development microservice node. Different from FIG. 1 , as shown in FIG. 2 , the public microservice node 201 in FIG. 2 is also deployed with a running instance of the microservice 210 , and other parts are the same as those in FIG. 1 . As described above, when the development microservice node 203 begins testing the running instance of the microservice 210, this may involve the running instance of the microservice 220. Therefore, when the running example of the microservice is started, the microservice name of the microservice is registered on the microservice registration server 202 . The microservice registration server 202 resolves the microservice name and obtains the associated IP address (the IP address of the public microservice node 201). The development microservice node 203 periodically obtains the associated IP address from the microservice registration server 202 . The development microservice node 203 selects the IP address of the public microservice node 201 to call the running instance of the microservice 220 on the public microservice node 201 . When the running instance of microservice 220 is invoked, it may in turn involve the running instance of microservice 210 . Therefore, the development microservice node 203 queries the microservice registration server 202 for the microservice name of the microservice 210 . The microservice registration server 202 resolves the microservice name of the microservice 210. In this case, since the running instance of the microservice 210 is deployed on the public microservice node 201 and the development microservice node 203 at the same time, the microservice The service name is associated with the IP addresses of the two microservice nodes. Therefore, the development microservice node 203 will obtain the IP addresses of two or more microservice nodes. After obtaining multiple IP addresses (eg, two) associated with the microservice name of the microservice 210, the microservice node 203 will preferentially route to its own IP address (the IP address of the microservice node 203), thereby invoking the deployment The running instance of the microservice 210 on the local microservice node is developed, so that the local developer can call the running instance of the microservice 210 on the local development microservice node 203 .

FIG. 3 shows a microservice development method 300 applied to develop a microservice node according to an embodiment of the present invention. As shown in FIG. 3 , the method includes three steps. Step S301 deploys a running instance of the microservice; step S302 registers the IP address of the development microservice node and the microservice name of the deployed microservice to the microservice registering a server; and step S303 initiating a test on the running instance of the microservice.

In step S301, the development microservice node deploys a running instance of the microservice thereon. Here, one or more running instances of the microservice to be tested can be deployed without deploying all the running instances of the related microservices on the development microservice node. The running instance of the microservice on the development microservice node is private and accessible by the developer.

In step S302, the development microservice node registers its IP address and the microservice name of the microservice deployed on it with the microservice registration server. When the running instance of the microservice is started, the microservice name of the microservice and the IP address of the node where the microservice is deployed will be registered on the microservice registration server and associated as a mapping relationship. The development microservice node queries the microservice name on the microservice registration server, and then the microservice registration server can parse the microservice name and obtain the IP addresses on which the microservice to which the microservice name belongs is deployed.

In step S303, the development microservice node will initiate a test on the running instance of the deployed microservice. The testing of the running instance of the deployed microservice may involve a running instance of the microservice that is not deployed on the development microservice node. In this case, the development microservice node will invoke the running instance of the microservice deployed on the public microservice node.

The invocation method specifically includes that the development microservice node registers the microservice name of the microservice called by the test with the microservice registration server. The microservice registration server will resolve the microservice name and obtain the IP address associated with the microservice name, that is, the IP address of the public microservice node where the running instances of multiple microservices are deployed. The development microservice node will periodically obtain the associated IP address (for example, the IP address of the public microservice node) from the microservice registration server, so the development microservice node selects the IP address of the public microservice node to call and deploy it on the public microservice node The running instance of the microservice on the server, so as to realize the test of the running example of the microservice.

In addition, when the microservice registration server parses the microservice name and finds that the microservice name is associated with multiple IP addresses, the development microservice node will obtain the multiple IP addresses. In the case where multiple IP addresses include the IP address of the development microservice node, the development microservice node will preferentially select the IP address of the development microservice node to call the running example of the microservice for testing.

In this way, it is not necessary to deploy all the running examples of microservices on the development microservice nodes, and at the same time, through the running examples of publicly accessible microservices, multiple development microservice nodes can realize the running examples of microservices. Invoke and develop in parallel. The method according to the present invention operates under the Spring Cloud microservice framework.

FIG. 4 shows a microservice development method 400 applied to a public microservice node according to an embodiment of the present invention. As shown in Figure 4, the method includes two steps, step S401 deploys a running instance of the microservice, wherein the running instance of the microservice keeps running for other nodes to test; step S402 deploys the public microservice node The IP address and the microservice name of the deployed microservice are registered with the microservice registration server.

In step S401, the public microservice node deploys a plurality of running instances of the microservice thereon, and the specific deployment quantity may depend on the computing capability of the public microservice node. Thus, the public microservice node becomes the running pool of the running examples of the public microservice. Other nodes can invoke the required running instance of the microservice from the common pool, wherein the running instance of the microservice is publicly accessible.

In step S402, the public microservice node registers its IP address and the microservice name of the microservice deployed on it with the microservice registration server. The IP address of the public microservice node is associated with the microservice name of the microservice deployed thereon on the microservice registration server.

When another microservice node invokes the running instance of the microservice on the public microservice node, the running instance of the microservice on the public microservice node may involve running instances of other microservices. In this case, public microservice nodes can call running instances of other microservices. The specific calling method is similar to the calling method in method 300 .

FIG. 5 shows a microservice development system 500 applied to develop a microservice node according to an embodiment of the present invention. As shown in FIG. 5, the method includes three modules, a deployment module 501, which deploys a running instance of a microservice; a registration module 502, which registers the IP address of the development microservice node and the microservice name of the deployed microservice is registered with the microservice registration server; and a test module 503, the test module 503 initiates a test on the running instance of the microservice.

The deployment module 501 deploys a running instance of the microservice thereon. Here, one or more running instances of the microservice to be tested can be deployed without deploying all the running instances of the related microservices on the development microservice node. The running instance of the microservice on the development microservice node is private and accessible by the developer.

The registration module 502 registers its IP address and the microservice name of the microservice deployed thereon with the microservice registration server. On the microservice registry server, the IP address will be associated with the microservice name. The development microservice node queries the microservice name on the microservice registration server, and then the microservice registration server can parse the microservice name to obtain the IP addresses on which the microservice to which the microservice name belongs is deployed.

The testing module 503 will initiate testing of the running instance of the deployed microservice. The testing of the running instance of the deployed microservice may involve a running instance of the microservice that is not deployed on the development microservice node. In this case, the development microservice node will invoke the running instance of the microservice deployed on the public microservice node.

Optionally, system 500 can also perform calls to microservices. The calling method specifically includes that the registration module 502 registers the microservice name of the microservice called by the test with the microservice registration server. The microservice registration server will resolve the microservice name and obtain the IP address associated with the microservice name, that is, the IP address of the public microservice node where the running instances of multiple microservices are deployed. The system 500 obtains the associated IP address, that is, the IP address of the public microservice node, from the microservice registration server. The testing module 503 selects the IP address of the public microservice node to call the running instance of the microservice deployed on the public microservice node, so as to test the running instance of the microservice.

In addition, when the microservice registration server parses the microservice name and finds that the microservice name is associated with multiple IP addresses, the system 500 obtains the multiple IP addresses from the microservice registration server. In the case where the multiple IP addresses include the IP address of the development microservice node, the testing module 503 will preferentially select the IP address of the development microservice node to call the running example of the microservice for testing.

FIG. 6 shows a microservice development system 600 applied to a public microservice node according to an embodiment of the present invention. As shown in FIG. 6, the method includes two modules, a deployment module 601, which deploys a running instance of a microservice, wherein the running instance of the microservice keeps running for other nodes to test; a registration module 602, the registration module 602 registers the IP address of the public microservice node and the microservice name of the deployed microservice with the microservice registration server.

The deployment module 601 deploys a plurality of running instances of microservices thereon, and the specific deployment quantity may depend on the computing capability of the public microservice nodes. Thus, the public microservice node becomes the running pool of the running examples of the public microservice. Other nodes can invoke the required running instance of the microservice from the common pool, wherein the running instance of the microservice is publicly accessible.

The registration module 602 registers its IP address and the microservice name of the microservice deployed thereon with the microservice registration server. The IP address of the public microservice node is associated with the microservice name of the microservice deployed thereon on the microservice registration server.

When another microservice node invokes the running instance of the microservice on the public microservice node, the running instance of the microservice on the public microservice node may involve running instances of other microservices. Optionally, in this case, system 600 may invoke running instances of other microservices. Specifically, the system can obtain the IP address from the microservice registration server, so as to select the IP address for invocation. The specific manner is similar to that in the system 500 .

Although the embodiments of the method and system for microservice development have been described above, the present invention is not limited to these embodiments, and the present invention can also be implemented in the following manner: a computer device for executing the above method or a The form of a computer program for executing the above-described method, the form of a computer program for realizing the functions of the above-described apparatus, or the form of a computer-readable recording medium on which the computer program is recorded.

FIG. 7 shows a computer device for the above-mentioned data encryption and decryption method according to an embodiment of the present invention. As shown in FIG. 7 , computer device 700 includes memory 701 and processor 702 . Although not shown, computer device 700 also includes a computer program stored on memory 701 and executable on processor 702 . When the processor executes the program, the steps shown in FIG. 1 , FIG. 2 , FIG. 3 and FIG. 4 are simultaneously implemented.

In addition, as described above, the present invention can also be implemented as a recording medium in which a program for causing a computer to execute the data encryption/decryption method as described above is stored.

Here, as the recording medium, disks (for example, magnetic disks, optical disks, etc.), cards (for example, memory cards, optical cards, etc.), semiconductor memories (for example, ROM, nonvolatile memory, etc.), tapes, etc., can be used. Types (eg, magnetic tapes, cassette tapes, etc.) and other recording media.

By recording and distributing a computer program for causing a computer to execute the data encryption/decryption method in the above-described embodiment or a computer program for causing a computer to realize the function of the data encryption/decryption method in the above-described embodiment in these recording media, it is possible to reduce costs. Low cost and improved portability and versatility.

Moreover, the above-mentioned recording medium is loaded on the computer, the computer program recorded in the recording medium is read out by the computer and stored in the memory, the processors (CPU: Central Processing Unit), MPU: Micro Processing Unit (microprocessing unit) reads the computer program from the memory and executes it, thereby executing the data masking and restoring method in the above-mentioned embodiment and realizing the functions of the device of the data masking and restoring method in the above-mentioned embodiment.

It should be understood by those skilled in the art that the present invention is not limited to the above-described embodiments, and the present invention may be embodied in many other forms without departing from the spirit and scope thereof. Accordingly, the examples and embodiments shown are to be regarded as illustrative rather than restrictive, and various modifications are possible within the present invention without departing from the spirit and scope of the invention as defined by the appended claims. with replacement.

Claims

A microservice development method applied to the development of microservice nodes, characterized in that the method comprises: deploying a running instance of the microservice;

registering the IP address of the development microservice node and the microservice name of the deployed microservice with the microservice registration server; and

A test of the running instance of the microservice is initiated.
The microservice development method for developing a microservice node according to claim 1, wherein the IP address of the development microservice node is associated with the microservice name of the microservice on the microservice registration server.
The microservice development method for developing a microservice node according to claim 2, wherein the running instance of the microservice is privately accessed.
The microservice development method for developing a microservice node according to claim 3, wherein when a test of the running instance of the microservice is initiated, the development microservice node calls and deploys on a public microservice node A running instance of the microservice.
The microservice development method for developing a microservice node according to claim 4, wherein invoking the running instance of the microservice deployed on the public microservice node comprises: the development microservice node queries the microservice registration server The microservice name of the microservice called by the test.
The microservice development method for developing a microservice node according to claim 5, wherein the development microservice node obtains an IP address associated with the microservice name from the microservice registration server, wherein the IP The address includes the IP address of the public microservice node.
The microservice development method for developing microservice nodes according to claim 6, wherein the development microservice node selects the IP address of the public microservice node for testing, so as to call the microservices deployed on the public microservice node A running instance of the service.
The microservice development method for developing a microservice node according to claim 6, wherein when the IP address further includes the IP address of the development microservice node, the development microservice node preferentially selects the development microservice node The IP address to call the running example of the microservice for testing.
The microservice development method for developing a microservice node according to claim 8, wherein the development microservice node is a computing node composed of one or more entity computers.
The microservice development method according to any one of claims 1-9, wherein the method runs under the Spring Cloud microservice framework.
A microservice development method applied to a public microservice node, characterized in that the method comprises: deploying a running instance of the microservice, wherein the running instance of the microservice keeps running for other nodes to test;

Register the IP address of the public microservice node and the microservice name of the deployed microservice with the microservice registration server.
The microservice development method for a public microservice node according to claim 11, wherein the IP address of the public microservice node is associated with the microservice name of the microservice on the microservice registration server.
The microservice development method for a public microservice node according to claim 12, wherein the running instance of the microservice is publicly accessible.
The microservice development method for a public microservice node according to claim 13, wherein the public microservice node obtains the IP address associated with the microservice name from the microservice registration server.
The microservice development method for a public microservice node according to claim 14, wherein the public microservice node selects the acquired IP address to invoke the running instance of the microservice deployed on other nodes.
The microservice development method for a public microservice node according to claim 15, wherein the public microservice node is a computing node composed of one or more entity computers.
The microservice development method according to any one of claims 11-16, wherein the method runs under the Spring Cloud microservice framework.
A micro-service development system applied to the development of micro-service nodes, characterized in that the system comprises: a deployment module, wherein the deployment module deploys a running instance of the micro-service;

a registration module, which registers the IP address of the development microservice node and the microservice name of the deployed microservice to the microservice registration server; and

A test module, the test module initiates a test of the running instance of the microservice.
The microservice development system for developing a microservice node according to claim 18, wherein the IP address of the development microservice node is associated with the microservice name of the microservice on the microservice registration server.
The microservice development system for developing microservice nodes according to claim 19, wherein the running instance of the microservice is privately accessed.
The microservice development system for developing microservice nodes according to claim 20, wherein when the test module initiates a test on the running instance of the microservice, the test module invokes the deployment in the public microservice A running instance of the microservice on the node.
The microservice development system for developing microservice nodes according to claim 21, wherein the test module invoking the running instance of the microservice deployed on the public microservice node comprises that the registration module registers with the microservice The server queries the microservice name of the microservice called by the test.
The microservice development system for developing microservice nodes according to claim 22, wherein the registration module obtains an IP address associated with the microservice name from the microservice registration server, wherein the IP address includes The IP address of the public microservice node.
The microservice development system for developing microservice nodes according to claim 23, wherein the test module selects the IP address of the public microservice node for testing, so as to call the microservices deployed on the public microservice node. Run the instance.
The microservice development system for developing microservice nodes according to claim 23, wherein when the IP address further includes the IP address of the development microservice node, the test module preferentially selects the IP of the development microservice node address to call the running example of the microservice for testing.
The microservice development system for developing microservice nodes according to claim 25, wherein the development microservice nodes are computing nodes composed of one or more entity computers.
The microservice development system according to any one of claims 18-26, wherein the system runs under the Spring Cloud microservice framework.
A microservice development system applied to a public microservice node, characterized in that the system comprises: a deployment module, the deployment module deploys a running instance of the microservice, wherein the running instance of the microservice keeps running for the purpose of Other node tests;

A registration module, which registers the IP address of the public microservice node and the microservice name of the deployed microservice with the microservice registration server.
The microservice development system for a public microservice node according to claim 28, wherein the IP address of the public microservice node is associated with the microservice name of the microservice on the microservice registration server.
The microservice development system for a public microservice node of claim 29, wherein the running instance of the microservice is publicly accessible.
The microservice development system for a public microservice node according to claim 30, wherein the registration module obtains the IP address associated with the microservice name from the microservice registration server.
The microservice development system for a public microservice node according to claim 31, wherein the system selects the acquired IP address to invoke the running instance of the microservice deployed on other nodes.
The microservice development system for a public microservice node according to claim 32, wherein the public microservice node is a computing node composed of one or more entity computers.
The microservice development system of any one of claims 28-33, wherein the system runs under the Spring Cloud microservices framework.
A computer device, comprising a memory, a processor and a computer program stored in the memory and running on the processor, characterized in that, when the processor executes the program, any one of claims 1 to 17 is realized when the processor executes the program. the steps of the method.
A recording medium on which a computer program is stored, characterized in that the program is executed by a computer to implement the steps of the method according to any one of claims 1 to 17.