CN115955506A - Micro-service publishing method, device, system and computer readable storage medium - Google Patents

Abstract

The application discloses a micro-service publishing method, a device and a system and a computer readable storage medium, wherein the method is applied to a micro-service publishing system, and the micro-service publishing system comprises a management terminal and at least one client terminal; the management terminal responds to a micro-service issuing instruction which is generated on a management interface and aims at a target client, and sends a micro-service issuing request to the client corresponding to the target client, wherein the micro-service issuing request comprises file storage information of the target micro-service to be issued; and after receiving the micro-service release request, the client acquires a target micro-service file according to the file storage information of the target micro-service and executes service release operation based on the target micro-service file. Therefore, service release to different clients can be managed in a unified mode, one-key release of micro services can be achieved, resource consumption is reduced, and the operation is simple and convenient.

Description

Microservice publishing method, device, system, and computer-readable storage medium

technical field

The present invention relates to the technical field of microservices, in particular to a microservice publishing method, device, system and computer-readable storage medium.

Background technique

The microservice architecture is split according to business functions, and the same business functions are placed in a microservice project to reduce service coupling and facilitate development and maintenance by developers. Microservice publishing methods can generally be divided into two types: one is to manually upload locally generated microservice files to the server, and start and stop microservices through the command line; the other is to deploy a set of service publishing tools that consume additional resources. Based on the code warehouse branch, pull the latest code, execute a series of service publishing intermediate processes, such as code specification, code vulnerability scanning, unit testing, etc., then execute the compilation and packaging command to obtain the target file, and then execute the corresponding service startup command to back up the target files, etc., and finally complete the service release.

However, since many small projects may deploy a set of services independently based on some functions of a larger project, it may be on a cloud environment or on a client company server. Server resources are often limited, only enough to deploy application services, and the code The warehouse is an intranet server. At this time, the release of the service is often deployed by a dedicated developer or operation and maintenance personnel through the command line. The service version is inconvenient to view, and the version rollback operation is not intuitive and easy to misuse. In addition, some small projects hatched from large-scale projects often have fewer developers. If the deployment personnel and developers are separated, there will be more links to release one version at a time, increasing communication costs and reducing efficiency. In addition, if the developers are completely allowed to operate by themselves, the requirements for the developers will be higher, and the permissions will not be well controlled, and the possibility of errors will increase. Therefore, the existing microservice publishing methods have problems such as high resource consumption and complicated operations.

Contents of the invention

The purpose of this application is to provide a microservice publishing method, device, system and computer-readable storage medium, which can uniformly manage service publishing to different customers, and realize one-click publishing of microservices, which reduces resource consumption and is easy to operate convenient.

To achieve the above purpose:

In the first aspect, the embodiment of the present application provides a microservice publishing method, which is applied to a microservice publishing system, the microservice publishing system includes a management terminal and at least one client, and the method includes the following steps:

The management terminal sends a microservice publishing request to the client corresponding to the target customer in response to the microservice publishing instruction for the target customer generated on the management interface, and the microservice publishing request includes the file of the target microservice to be published store information;

After receiving the microservice publishing request, the client acquires the target microservice file according to the file storage information of the target microservice, and executes a service publishing operation based on the target microservice file.

Optionally, the management terminal further includes:

The management terminal acquires user login information, and displays service operation items for which the user has operation authority on the management interface according to the user login information.

Optionally, before the client receives the microservice release request, it may further include:

The client receives the target microservice file sent by the management terminal, and performs authority verification based on the key pair issued by the management terminal in advance. If the verification is passed, the target microservice file is stored, and the Sending the file storage information of the target microservice file to the management terminal;

The management terminal receives and records the file storage information of the target microservice file.

Optionally, the method also includes:

The client executes a pre-operation and/or a post-operation for publishing a service for the target microservice; the pre-operation includes at least one of the following: backing up the current microservice file corresponding to the target microservice, stopping The target microservice clears cached data; the post-operation includes at least one of the following: outputting a service release reminder message; refreshing cached data.

Optionally, the method also includes:

The management terminal periodically sends a heartbeat packet to the client, and performs abnormal detection on the client according to the receiving situation of the heartbeat packet.

In the second aspect, the embodiment of the present application provides a microservice publishing method, which is applied to the management end, and the method includes:

Responsive to microservice publishing instructions for target customers generated at the management interface;

Sending a microservice publishing request to the client corresponding to the target client, where the microservice publishing request includes file storage information of the target microservice to be published.

Optionally, the method further includes: acquiring user login information, and displaying service operation items for which the user has operation authority on the management interface according to the user login information.

Optionally, the method also includes:

sending the target microservice file to the client;

receiving and recording the file storage information of the target microservice file sent by the client.

Optionally, the method also includes:

Periodically send heartbeat packets to the client, and perform anomaly detection on the client according to the reception of the heartbeat response packet.

In the third aspect, the embodiment of the present application provides a method for publishing a microservice, which is applied to a client, and the method includes:

receiving a microservice publishing request sent by the management terminal; the microservice publishing request includes file storage information of the target microservice to be published;

A target microservice file is acquired according to the file storage information of the target microservice, and a service publishing operation is performed based on the target microservice file.

Optionally, the method also includes:

receiving the target microservice file sent by the management terminal, and performing permission verification based on the key pair issued by the management terminal in advance; if the verification is passed, storing the target microservice file, and The file storage information of the service file is sent to the management terminal.

Optionally, the method also includes:

Executing pre-operations and/or post-operations for publishing services for the target microservice; the pre-operations include at least one of the following: backing up the current microservice file corresponding to the target microservice, stopping the target microservice Serving, clearing cached data; the post-operation includes at least one of the following: outputting a service release reminder message; refreshing cached data.

In the fourth aspect, the embodiment of the present application provides a microservice publishing system, including a management terminal and at least one client; wherein, the management terminal and the client are respectively used to execute any one of the second aspect and the third aspect The corresponding microservice publishing method described in item.

In a fifth aspect, the embodiment of the present application provides a microservice publishing device, including: a processor and a memory storing a computer program, and when the processor runs the computer program, the steps of the above microservice publishing method are realized.

In a sixth aspect, the embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above microservice publishing method are implemented.

The microservice publishing method, device, system, and computer-readable storage medium provided by the embodiments of the present application, the method is applied to a microservice publishing system, and the microservice publishing system includes a management terminal and at least one client; the management terminal In response to the microservice publishing instruction for the target customer generated on the management interface, sending a microservice publishing request to the client corresponding to the target customer, the microservice publishing request includes file storage information of the target microservice to be published; After receiving the microservice publishing request, the client acquires the target microservice file according to the file storage information of the target microservice, and executes a service publishing operation based on the target microservice file. In this way, service publishing to different customers can be managed in a unified manner, and one-click publishing of microservices can be realized, resource consumption is reduced, and the operation is simple and convenient.

Description of drawings

FIG. 1 is a first schematic flow diagram of a microservice publishing method provided by an embodiment of the present invention;

FIG. 2 is a second schematic flow diagram of a microservice publishing method provided by an embodiment of the present invention;

FIG. 3 is a third schematic flow diagram of a microservice publishing method provided by an embodiment of the present invention;

FIG. 4 is a schematic diagram of the architecture of the microservice publishing system provided by the embodiment of the present invention;

Fig. 5 is a schematic diagram of the user authority system in the embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a microservice publishing device provided by an embodiment of the present invention.

Detailed ways

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numerals in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present application as recited in the appended claims.

It should be noted that, in this document, the term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a..." does not exclude the existence of other identical elements in the process, method, article, or device that includes the element. In addition, different implementations of the present application Components, features, and elements with the same name in the example may have the same meaning, or may have different meanings, and the specific meaning shall be determined based on the explanation in the specific embodiment or further combined with the context in the specific embodiment.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be called second information, and similarly, second information may also be called first information. Depending on the context, the word "if" as used herein may be interpreted as "at" or "when" or "in response to a determination". Furthermore, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising", "comprising" indicate the presence of stated features, steps, operations, elements, components, items, species, and/or groups, but do not exclude one or more other features, steps, operations, The existence, occurrence or addition of an element, component, item, species, and/or group. The terms "or" and "and/or" as used herein are to be construed as inclusive, or to mean either one or any combination. Thus, "A, B or C" or "A, B and/or C" means "any of the following: A; B; C; A and B; A and C; B and C; A, B and C" . Exceptions to this definition will only arise when combinations of elements, functions, steps or operations are inherently mutually exclusive in some way.

It should be understood that although the various steps in the flow chart in the embodiment of the present application are displayed sequentially as indicated by the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figure may include multiple sub-steps or multiple stages, these sub-steps or stages are not necessarily executed at the same time, but may be executed at different times, and the execution order is not necessarily sequential Instead, it may be performed alternately or alternately with at least a part of other steps or sub-steps or stages of other steps.

It should be noted that, in this article, step codes such as S101 and S102 are used, the purpose of which is to express the corresponding content more clearly and concisely, and does not constitute a substantive limitation on the order. Those skilled in the art may, during specific implementation, S102 will be executed first, followed by S101, etc., but these should be within the protection scope of this application.

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

In the following description, the use of suffixes such as 'module', 'part' or 'unit' for denoting elements is only for facilitating the description of the present application and has no specific meaning by itself. Therefore, 'module', 'part' or 'unit' may be mixedly used.

Referring to Fig. 1, a microservice publishing method provided by the embodiment of the present application is applied to a microservice publishing system, and the microservice publishing system includes a management terminal and at least one client; the microservice publishing method provided by the embodiment of the present application include:

Step S101: The management terminal sends a microservice publishing request to the client corresponding to the target customer in response to the microservice publishing instruction for the target customer generated on the management interface, and the microservice publishing request includes the target microservice to be published Files store information.

Optionally, the management terminal can be a computer or other intelligent terminal used by managers or technicians, and the management terminal can provide and display a management interface through which microservices corresponding to different customers can be managed, Such as publishing microservices, deleting microservices, etc. The client can be a computer or other intelligent terminal on the client side. Understandably, based on the needs of different customers, small projects hatched from large projects can be deployed to corresponding customers in the form of microservices. At the same time, the number of projects and microservices deployed to customers can be displayed on the management interface corresponding menu. For example, if customer A has two projects, and each project has two microservices, the information of customer A can be displayed in the customer menu, and the above two microservices can be displayed in the project menu of customer A. It should be noted that the management interface may provide an operation menu for different microservices of different customers, and the operation menu may include service operation items such as publishing (or modifying), deleting, and the like. When the user enters an operation on the management interface to choose to publish a certain microservice of the target customer, the management terminal obtains the microservice release instruction for the target customer generated on the management interface, and sends the instruction to the client corresponding to the target customer Sending a microservice publishing request, where the microservice publishing request includes file storage information of the target microservice to be published. Optionally, the target client is the client to which the micro-service to be released belongs, and the management terminal can determine the target client’s corresponding The registration address of the client, and then send a microservice publishing request to the client corresponding to the target client. It should be noted that the publishing of microservices in this embodiment may also be called publishing of services.

In one embodiment, before the management terminal responds to microservices generated on the management interface to issue instructions for target customers, the management terminal further includes: the management terminal obtains user login information, and according to the user login information, the management interface Display the service operation items for which the user has operation authority. Understandably, different operation permissions can be set for different users. The operation permissions can be classified according to customer, project, service, and operation. If the customer permission is assigned, all services and all operations under the customer have permission . For example, some users can only manage all services under customer A, while others can only manage all services under customer B, or, some users can only manage project C of customer A, while others can only manage projects of customer A D; Or, some users can only view microservices, and other users can only publish microservices. Optionally, after obtaining the user login information, the management terminal may determine the user's operation authority according to the user login information, and then display the service operation items for which the user has operation authority on the management interface. For example, if it is determined according to the user login information that the user only has the operation authority for customer A, then only the service operation items for customer A, such as publishing and deleting, can be displayed on the management interface. In this way, the service operation items displayed on the management interface are determined according to the user's operation authority, which improves management security and further reduces resource consumption.

In an embodiment, before the client receives the microservice release request, it further includes:

The client receives the target microservice file sent by the management terminal, and performs authority verification based on the key pair issued by the management terminal in advance. If the verification is passed, the target microservice file is stored, and the Sending the file storage information of the target microservice file to the management terminal;

The management end records the file storage information of the target microservice file.

Optionally, after the management terminal determines the file corresponding to the target microservice to be published, that is, the target microservice file, it can first send the target microservice file to the client corresponding to the target client, and correspondingly, the The client receives the target microservice file sent by the management terminal, and performs authority verification based on the key pair issued by the management terminal in advance. If the verification is passed, the target microservice file is stored, and the Send the file storage information of the target microservice file to the management terminal. Optionally, the target microservice file is encrypted and sent by the management terminal, and the client uses the key pair to verify the authority of the target microservice file, and if the verification is passed, the target microservice file is decrypted. Microservice file, and store the target microservice file according to the project to which the target microservice belongs, service name, receiving time, and remarks. The key pair is issued by the management terminal to the client according to preset rules when the client registers with the management terminal. Optionally, the client may store the target microservice file in a local disk, or store the target microservice file in an object storage server such as an NFS file server or an AWS server, that is, the target The storage address and storage method of microservice files can be set according to the actual situation. Meanwhile, the file storage information may include but not limited to the project to which the target microservice belongs, service name, receiving time, notes, storage address, storage method, etc. After the management end receives the file storage information of the target microservice file sent by the client, it records the file storage information of the target microservice file, so that when the target microservice needs to be published later, the The file storage information is notified to the client, and at the same time, unified information management is implemented by the management terminal. In this way, after the authority verification is passed, the client stores the target microservice file and uploads the corresponding file storage information to the management terminal, which improves the security of microservice release and improves the convenience of information management.

Step S102: After receiving the microservice publishing request, the client acquires the target microservice file according to the file storage information of the target microservice, and executes a service publishing operation based on the target microservice file.

Optionally, after receiving the microservice release request sent by the management end, the client can obtain the target microservice file according to the file storage information of the target microservice in the microservice release request , and perform a service publishing operation based on the target microservice file, so as to realize publishing the target microservice.

To sum up, in the microservice release method provided by the above embodiment, different clients can be managed uniformly through the management terminal, and each client only needs to deploy microservices to achieve the effect of management service release, which greatly reduces resource costs and enables unified management Publish the services of different customers, and realize the one-click release of microservices, which reduces resource consumption and is easy and convenient to operate.

In one embodiment, the method also includes:

The client executes a pre-operation and/or a post-operation for publishing a service for the target microservice; the pre-operation includes at least one of the following: backing up the current microservice file corresponding to the target microservice, stopping The target microservice clears cached data; the post-operation includes at least one of the following: outputting a service release reminder message; refreshing cached data.

Optionally, before the client executes the service publishing operation based on the target microservice file, it may perform a pre-operation of service publishing for the target microservice, such as backing up the current microservice corresponding to the target microservice files, stop said target microservice, clear cached data, etc. After the client executes the service release operation based on the target microservice file, it can perform post-operations for service release for the target microservice, such as outputting a service release reminder message, refreshing cached data, and so on. Optionally, the purpose of backing up the current microservice file corresponding to the target microservice is to ensure that the historical service version rollback can be realized later, that is, after the management terminal executes the service release operation based on the target microservice file, if If the current microservice file corresponding to the target microservice needs to be reused for service publication later, the corresponding operation can be realized through the backed up current microservice file corresponding to the target microservice. In this way, by performing the pre-operation and/or post-operation of service publishing for the target microservice, the convenience of microservice publishing is improved.

In one embodiment, the method also includes:

The management terminal periodically sends a heartbeat packet to the client, and performs abnormal detection on the client according to the receiving situation of the heartbeat packet.

Optionally, in order to maintain a list of healthy clients and give an early warning when there is an abnormality, the management end may periodically send a heartbeat packet to the client based on the registered address of the client, and send a heartbeat packet to the client according to the receiving situation of the heartbeat packet. The client performs anomaly detection. Optionally, the condition of receiving the heartbeat packet may include whether the heartbeat response packet fed back by the client is received, and whether the interval between receiving the heartbeat response packet fed back by the client meets the preset duration requirement, and the like. Optionally, when an abnormality of the client is detected, an alarm message may be output to notify the user to handle it in time. In this way, the convenience and timeliness of managing microservices of different customers are improved.

Referring to Fig. 2, it is a microservice publishing method provided by the embodiment of the present application. The microservice publishing method can be executed by a microservice publishing device provided in the embodiment of the present application. The microservice publishing device can use software and/or In this embodiment, the microservice publishing device is used as the management terminal as an example. The microservice publishing method provided in this embodiment includes:

Step S201: issuing instructions in response to microservices for target customers generated on the management interface.

Optionally, the management terminal can be a computer or other intelligent terminal used by managers or technicians, and the management terminal can provide and display a management interface through which microservices corresponding to different customers can be managed, Such as publishing microservices, deleting microservices, etc. Based on the needs of different customers, small projects hatched from large projects can be deployed to corresponding customers in the form of microservices. At the same time, corresponding menus can be displayed on the management interface for the number of projects and microservices deployed to customers. For example, if customer A has two projects, and each project has two microservices, the information of customer A can be displayed in the customer menu, and the above two microservices can be displayed in the project menu of customer A. It should be noted that the management interface may provide an operation menu for different microservices of different customers, and the operation menu may include service operation items such as publishing (or modifying), deleting, and the like. When the user inputs an operation on the management interface to choose to publish a certain microservice of the target customer, the management terminal obtains the microservice publishing instruction for the target customer generated on the management interface.

In an embodiment, the method further includes: acquiring user login information, and displaying service operation items for which the user has operation authority on the management interface according to the user login information. Understandably, different operation permissions can be set for different users. The operation permissions can be classified according to customer, project, service, and operation. If the customer permission is assigned, all services and all operations under the customer have permission . For example, some users can only manage all services under customer A, while others can only manage all services under customer B, or, some users can only manage project C of customer A, while others can only manage projects of customer A D; Or, some users can only view microservices, and other users can only publish microservices. Optionally, after obtaining the user login information, the management terminal may determine the user's operation authority according to the user login information, and then display the service operation items for which the user has operation authority on the management interface. For example, if it is determined according to the user login information that the user only has the operation authority for customer A, then only the service operation items for customer A, such as publishing and deleting, can be displayed on the management interface. In this way, the service operation items displayed on the management interface are determined according to the user's operation authority, which improves management security and further reduces resource consumption.

In one embodiment, the method also includes:

sending the target microservice file to the client;

receiving and recording the file storage information of the target microservice file sent by the client.

Optionally, after the management terminal determines the file corresponding to the target microservice to be published, that is, the target microservice file, it may first send the target microservice file to the client corresponding to the target client. After the management end receives the file storage information of the target microservice file sent by the client, it records the file storage information of the target microservice file, so that when the target microservice needs to be published later, the The file storage information is notified to the client, and at the same time, unified information management is implemented by the management terminal. The file storage information may include, but is not limited to, the project to which the target microservice belongs, service name, receiving time, remarks, storage address, storage method, and the like. In this way, the convenience of information management is improved.

Step S202: Sending a microservice publishing request to the client corresponding to the target client, the microservice publishing request including file storage information of the target microservice to be published.

Optionally, the management end sends a microservice publishing request to the client corresponding to the target client, and the microservice publishing request includes file storage information of the target microservice to be published. Optionally, the target client is the client to which the micro-service to be released belongs, and the management terminal can determine the target client’s corresponding The registration address of the client, and then send a microservice publishing request to the client corresponding to the target client.

To sum up, in the microservice release method provided by the above embodiment, different clients can be managed uniformly through the management terminal, and each client only needs to deploy microservices to achieve the effect of management service release, which greatly reduces resource costs and enables unified management Publish the services of different customers, and realize the one-click release of microservices, which reduces resource consumption and is easy and convenient to operate.

In one embodiment, the method also includes:

Sending heartbeat packets to the client periodically, and performing anomaly detection on the client according to the reception of the heartbeat packets.

Optionally, in order to maintain a list of healthy clients and give an early warning when there is an abnormality, the management end may periodically send a heartbeat packet to the client based on the registered address of the client, and send a heartbeat packet to the client according to the receiving situation of the heartbeat packet. The client performs anomaly detection. Optionally, the condition of receiving the heartbeat packet may include whether a heartbeat response packet is received, and whether the interval between receiving the heartbeat response packet satisfies a preset duration requirement, and the like. Optionally, when an abnormality of the client is detected, an alarm message may be output to notify the user to handle it in time. In this way, the convenience and timeliness of managing microservices of different customers are improved.

Referring to Fig. 3, it is a microservice publishing method provided by the embodiment of the present application. The microservice publishing method can be executed by a microservice publishing device provided in the embodiment of the present application. The microservice publishing device can use software and/or In this embodiment, the microservice publishing device is used as a client as an example. The microservice publishing method provided in this embodiment includes:

Step S301: Receive the microservice publishing request sent by the management terminal; the microservice publishing request includes the file storage information of the target microservice to be published.

Optionally, the client may be a computer or other intelligent terminal on the client side.

In one embodiment, the method also includes:

receiving the target microservice file sent by the management terminal, and performing permission verification based on the key pair issued by the management terminal in advance; if the verification is passed, storing the target microservice file, and The file storage information of the service file is sent to the management terminal.

Optionally, after the management terminal determines the file corresponding to the target microservice to be published, that is, the target microservice file, it can first send the target microservice file to the client corresponding to the target client, and correspondingly, the The client receives the target microservice file sent by the management terminal, and performs authority verification based on the key pair issued by the management terminal in advance. If the verification is passed, the target microservice file is stored, and the Send the file storage information of the target microservice file to the management terminal. Optionally, the target microservice file is encrypted and sent by the management terminal, and the client uses the key pair to verify the authority of the target microservice file, and if the verification is passed, the target microservice file is decrypted. Microservice file, and store the target microservice file according to the project to which the target microservice belongs, service name, receiving time, and remarks. The key pair is issued by the management terminal to the client according to preset rules when the client registers with the management terminal. Optionally, the client may store the target microservice file in a local disk, or store the target microservice file in an object storage server such as an NFS file server or an AWS server, that is, the target The storage address and storage method of microservice files can be set according to the actual situation. Meanwhile, the file storage information may include but not limited to the project to which the target microservice belongs, service name, receiving time, notes, storage address, storage method, etc. In this way, after the authority verification is passed, the client stores the target microservice file and uploads the corresponding file storage information to the management terminal, which improves the security of microservice release and improves the convenience of information management.

Step S302: Obtain the target microservice file according to the file storage information of the target microservice, and perform a service publishing operation based on the target microservice file.

Optionally, after receiving the microservice release request sent by the management end, the client can obtain the target microservice file according to the file storage information of the target microservice in the microservice release request , and perform a service publishing operation based on the target microservice file, so as to realize publishing the target microservice.

To sum up, in the microservice release method provided by the above embodiment, different clients can be managed uniformly through the management terminal, and each client only needs to deploy microservices to achieve the effect of management service release, which greatly reduces resource costs and enables unified management Publish the services of different customers, and realize the one-click release of microservices, which reduces resource consumption and is easy and convenient to operate.

In one embodiment, the method also includes:

Executing pre-operations and/or post-operations for publishing services for the target microservice; the pre-operations include at least one of the following: backing up the current microservice file corresponding to the target microservice, stopping the target microservice Serving, clearing cached data; the post-operation includes at least one of the following: outputting a service release reminder message; refreshing cached data.

Optionally, before the client executes the service publishing operation based on the target microservice file, it may perform a pre-operation of service publishing for the target microservice, such as backing up the current microservice corresponding to the target microservice files, stop said target microservice, clear cached data, etc. After the client executes the service release operation based on the target microservice file, it can perform post-operations for service release for the target microservice, such as outputting a service release reminder message, refreshing cached data, and so on. Optionally, the purpose of backing up the current microservice file corresponding to the target microservice is to ensure that the historical service version rollback can be realized later, that is, after the management terminal executes the service release operation based on the target microservice file, if If the current microservice file corresponding to the target microservice needs to be reused for service publication later, the corresponding operation can be realized through the backed up current microservice file corresponding to the target microservice. In this way, by performing the pre-operation and/or post-operation of service publishing for the target microservice, the convenience of microservice publishing is improved.

Based on the same inventive concept as the foregoing embodiments, this embodiment of the present application also provides a microservice publishing system, including a management terminal and at least one client; wherein, the management terminal and the client are respectively used to implement the The corresponding microservice publishing method described above.

Based on the same inventive concept as the foregoing embodiments, the foregoing embodiments will be described in detail below through a specific example.

Referring to Figure 4, the overall architecture diagram of the micro-service publishing system provided in this embodiment mainly includes two modules: the management terminal, which provides a unified management platform for service publishers. This platform is deployed within the company, and the deployment nodes can be expanded. Responsible for unified communication with customer nodes, unified authority control of service publishers, including menu authority, data authority, operation authority, etc.; client, responsible for receiving management node scheduling, receiving service files, performing service file backup storage, service publishing, and historical service versions Rollback, listen to service release events, perform service release pre-operations and service release post-operations. Wherein, different clients n correspond to client nodes n, and n is a positive integer.

Among them, the deployment of management nodes and the realization of main functions include:

The management node is deployed inside the company. The management node can be deployed on a single node, or according to the number of customer nodes, add service nodes registered with the service registration center, and be represented by the unified gateway to achieve the purpose of horizontal expansion.

The management node maintains the heartbeat of the customer node, regularly sends the heartbeat packet to the customer node through the registration address of the customer node, maintains the list of healthy nodes, and can give an early warning if there is any abnormality. Through the operation of the service publisher, the information is transmitted to the corresponding client node, and the client node responds to the corresponding operation event and makes a processing.

Refer to Figure 5, which is a schematic diagram of the user authority system. From top to bottom, there are customers, projects, services, and operation types, which are classified according to the tree structure. The maximum authority can be assigned according to the customer. If the customer permission is assigned, all services and operations under the customer have permission. The minimum authority can be assigned according to the specific operation of a certain service of a certain customer.

Customer node deployment and main function realization include:

The customer node is deployed in the customer company, and its main functions are to receive service files, back up service files, perform service publishing, service rollback operations, and respond to operational events.

The service file is transferred from the management node to the customer node through the Restful API interface call. The customer node performs authority verification through the pre-issued key pair. After the verification is passed, the service file is stored according to the service name, time and notes according to the project. The storage address can be stored on the local disk or NFS file server, AWS S3, Huawei obs and other object storage servers according to the customer's situation, and the result will be returned to the management node for record management by the management node.

Service release and rollback are based on the file address in the request parameter of the management node, the client node finds the target file, and then executes the customized service release operation, such as the Java service executes the corresponding start command, and the static resource is stored in the specified Proxy directories and more. According to customer needs, you can customize the pre-operation and post-operation of service release, clear the Redis cache, refresh the CDN cache, send service release message reminders, etc.

To sum up, in the microservice release method provided by this embodiment, the project service release plan deployed to customers is managed in a unified manner. The management nodes can adopt distributed deployment, and the customer nodes can deploy single-node or distributed deployment depending on the resource situation. Customer nodes and The management node can use Restful API interface communication to achieve the following effects: 1) A management service can manage different customer project nodes in a unified manner, and the customer project node only needs to deploy a microservice to achieve the effect of management service release, greatly reducing resource costs; 2) The performance of service publishing is fast and simple, with one-click release, one-click rollback, authority control, and operation supervision and audit; 3) Unified management services can be customized to meet the special needs of different customer service releases based on release events. That is to say, using the microservice release method with unified management and low resource consumption can reduce the resource requirements of the client server and achieve the purpose of unified management for multiple client projects. The service files based on storage can quickly release and roll back historical version services.

Based on the same inventive concept as the foregoing embodiments, the embodiment of the present invention provides a microservice publishing device, as shown in FIG. 6 , the device includes: a processor 310 and a memory 311 storing computer programs; The processor 310 is not used to refer to the number of the processor 310 as one, but only used to refer to the positional relationship of the processor 310 relative to other devices. In practical applications, the number of the processor 310 can be one or Multiple; similarly, the memory 311 illustrated in FIG. 6 also has the same meaning, that is, it is only used to refer to the positional relationship of the memory 311 relative to other devices. In practical applications, the number of the memory 311 can be one or more. When the processor 310 runs the computer program, the microservice publishing method applied to the above-mentioned device is realized.

The device may further include: at least one network interface 312 . The various components in the device are coupled together via a bus system 313 . It can be understood that the bus system 313 is used to realize connection and communication between these components. In addition to the data bus, the bus system 313 also includes a power bus, a control bus and a status signal bus. However, the various buses are labeled bus system 313 in FIG. 6 for clarity of illustration.

Wherein, the memory 311 may be a volatile memory or a non-volatile memory, and may also include both volatile and non-volatile memories. Among them, the non-volatile memory can be read-only memory (ROM, Read Only Memory), programmable read-only memory (PROM, Programmable Read-Only Memory), erasable programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory) Only Memory), Electrically Erasable Programmable Read-Only Memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), Magnetic Random Access Memory (FRAM, ferromagnetic random access memory), Flash Memory (Flash Memory), Magnetic Surface Memory , CD, or CD-ROM (Compact Disc Read-Only Memory); magnetic surface storage can be disk storage or tape storage. The volatile memory may be random access memory (RAM, Random Access Memory), which is used as an external cache. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM, Static Random Access Memory), Synchronous Static Random Access Memory (SSRAM, Synchronous Static Random Access Memory), Dynamic Random Access Memory Memory (DRAM, Dynamic Random Access Memory), Synchronous Dynamic Random Access Memory (SDRAM, Synchronous Dynamic Random Access Memory), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM, Double Data Rate Synchronous Dynamic Random Access Memory), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM, Enhanced Synchronous Dynamic Random Access Memory), Synchronous Connection Dynamic Random Access Memory (SLDRAM, SyncLink Dynamic Random Access Memory), Direct Memory Bus Random Access Memory (DRRAM, Direct Rambus Random Access Memory) . The memory 311 described in the embodiment of the present invention is intended to include but not limited to these and any other suitable types of memory.

The memory 311 in the embodiment of the present invention is used to store various types of data to support the operation of the device. Examples of such data include: any computer programs used to operate on the device, such as operating systems and applications; contacts data; phonebook data; messages; pictures; videos, etc. Among them, the operating system includes various system programs, such as framework layer, core library layer, driver layer, etc., for realizing various basic services and processing tasks based on hardware. The application program may include various application programs, such as a media player (Media Player), a browser (Browser), etc., for implementing various application services. Here, the program for realizing the method of the embodiment of the present invention may be included in the application program.

Based on the same inventive concept of the foregoing embodiments, the present embodiment also provides a computer storage medium in which a computer program is stored, and the computer storage medium may be a magnetic random access memory (FRAM, ferromagnetic random access memory) , Read-Only Memory (ROM, Read Only Memory), Programmable Read-Only Memory (PROM, Programmable Read-Only Memory), Erasable Programmable Read-Only Memory (EPROM, Erasable Programmable Read-Only Memory), Electrically Erasable Programmable read-only memory (EEPROM, Electrically Erasable Programmable Read-Only Memory), flash memory (FlashMemory), magnetic surface memory, optical disc, or memory such as CD-ROM (Compact Disc Read-Only Memory); also It may be various devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, and the like. When the computer program stored in the computer storage medium is run by the processor, the microservice publishing method applied to the above-mentioned device is realized. Please refer to the description of the embodiment shown in FIGS. 1-3 for the specific steps and procedures implemented when the computer program is executed by the processor, and details are not repeated here.

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

As used herein, the terms "comprises", "comprises" or any other variation thereof are intended to cover a non-exclusive inclusion of elements other than those listed and also other elements not expressly listed.

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (10)

1. A micro-service release method is characterized in that the method is applied to a micro-service release system, and the micro-service release system comprises a management end and at least one client end; the method comprises the following steps:

the management terminal responds to a micro-service issuing instruction which is generated on a management interface and aims at a target client, and sends a micro-service issuing request to the client corresponding to the target client, wherein the micro-service issuing request comprises file storage information of the target micro-service to be issued;

and after receiving the micro-service release request, the client acquires a target micro-service file according to the file storage information of the target micro-service, and executes service release operation based on the target micro-service file.

2. The method of claim 1, wherein the managing end responds to the micro-service for the target client issuing the instruction generated in the management interface, and further comprising:

and the management terminal acquires user login information and displays service operation items with operation authority of the user on the management interface according to the user login information.

3. The method of claim 1, wherein before the client receives the microservice publishing request, the method further comprises:

the client receives the target micro service file sent by the management terminal, carries out authority verification based on a key pair issued by the management terminal in advance, stores the target micro service file if the verification is passed, and sends file storage information of the target micro service file to the management terminal;

and the management terminal receives and records the file storage information of the target micro-service file.

4. The method according to any one of claims 1 to 3, further comprising:

the client executes the preposed operation and/or the postpositive operation of service release aiming at the target micro service; the pre-operation comprises at least one of: backing up a current micro service file corresponding to the target micro service, stopping the target micro service and emptying cache data; the post-operation comprises at least one of: the output service issues a reminding message; and refreshing the cached data.

5. The method according to any one of claims 1 to 3, further comprising:

and the management terminal periodically sends heartbeat packets to the client terminal and carries out abnormity detection on the client terminal according to the receiving condition of the heartbeat packets.

6. A micro-service publishing method is applied to a management end, and is characterized by comprising the following steps:

issuing an instruction in response to the micro-service for the target customer generated at the management interface;

and sending a micro-service publishing request to a client corresponding to the target client, wherein the micro-service publishing request comprises file storage information of the target micro-service to be published.

7. A micro-service issuing method is applied to a client, and is characterized by comprising the following steps:

receiving a micro-service release request sent by a management end; the micro-service publishing request comprises file storage information of a target micro-service to be published;

and acquiring a target micro-service file according to the file storage information of the target micro-service, and executing service release operation based on the target micro-service file.

8. A micro-service release system is characterized by comprising a management end and at least one client end; wherein the management end and the client end are respectively used for executing the corresponding micro-service publishing method of any one of claims 1-7.

9. A microservice publishing device, comprising: a processor and a memory storing a computer program which, when executed by the processor, implement the steps of the microservice publishing method of any of claims 1 to 7.

10. A computer-readable storage medium, characterized in that a computer program is stored which, when being executed by a processor, carries out the steps of the microservice publishing method according to any one of claims 1 to 7.

Images