CN115658109A - Microservice hot deployment method, system, electronic device and storage medium - Google Patents

Abstract

The embodiment of the application provides a method, a system, electronic equipment and a storage medium for deploying micro service heat, wherein the method comprises the steps of obtaining an application package, storing the application package in a storage device, loading the application package in the storage device to a specified file directory, creating a class loader of the application package, setting the class loader of an application driving file as the class loader created by the class loader of the application package, and loading the application driving file; the initialized spring boot container is associated with the application metadata, the associated comparison table is stored in the program context, the spring boot container is externally issued according to the rule of the spring external issuing service and is provided for external access, and the non-stop updating service can be realized, so that the condition that the whole application service is in an unavailable state due to the stop updating is avoided.

Description

Microservice hot deployment method, system, electronic device and storage medium

technical field

The present invention relates to the technical field of microservices, in particular to a Spring Boot-based microservice hot deployment method, system, electronic device and storage medium.

Background technique

With the rise of the microservice architecture, the traditional OSGI technology modular single architecture is gradually abandoned, and the development of microservice application technology with Springboot is becoming more and more widespread in the industry. Although microservices can achieve local service updates by reasonably dividing service boundaries, However, it still cannot meet the needs of hot deployment in certain business scenarios, such as implementing bug fixes and launching new functions without downtime.

At present, the general steps for updating and deploying applications in the industry are: first stop the old application, and back it up, then upload the new application, update the configuration, etc., and then start the new application. For systems that need to frequently update some interface services in the application, there will be several problems:

1. The version of the application file is not easy to manage. The difference between the old and new versions of the file content may be more or less jar packages, but updating an interface will result in an application package file, and the backup takes up too much space, and it also becomes difficult to manage. Get confused.

2. This kind of update must stop the service, and then start a new service. Frequent downtime for update deployment will seriously affect the operation of the system. Most companies have fixed downtime for maintenance and update time, and such frequent updates are not allowed at all.

In the industry, there is a servicemix framework that supports hot deployment applications, but it has been stopped for more than a few years, and it is not compatible with the current Spring boot application, and the JBI specification it follows is no longer suitable for the microservice architecture.

Contents of the invention

The invention provides a microservice hot deployment method, system, electronic equipment and storage medium, capable of updating services without stopping.

Technical scheme of the present invention is:

In the first aspect, the embodiment of the present application provides a microservice hot deployment method, characterized in that the method includes:

Obtaining an application package, the application package at least includes configuration file information satisfying the spring boot framework service, an application driver file whose content conforms to the spring boot standard and agreed directory rules, and application metadata that can identify the configuration content;

saving the application package to a storage device, and loading the application package in the storage device to a specified file directory;

Create the class loader of the application package, load the class loader into the class loader collection where the main application is located, and set the type of its class loader;

Setting the class loader of the application driver file as the class loader created by the class loader for creating the application package, using the class loader to load the application driver file;

Use spring boot to initialize the application package to obtain the spring boot container, associate the spring boot container with application metadata, and save the associated comparison table in the program context;

Refresh the service resource reference in the spring boot container, generate the service definition according to the rules of spring's external publishing service, and publish it externally.

Preferably, the configuration file information satisfying the spring boot framework service at least includes the service address, name, parameters, and return data of the spring boot framework.

Preferably, the application package is constructed by maven, ant or gradle construction tools, and the constructed program package is a jar package.

Preferably, the specific method for creating the class loader of the application package includes:

Create a UrlClassLoader instance;

Add the application package to the url collection of the instance, and set its class loader as the startup class loader.

Preferably, the application driver file is an application driver file in springContext.xml format.

Preferably, the application metadata information includes at least one of application name, application identifier, application version, service information and configuration information, wherein the service information includes at least one of external service quantity, service description and service type One, the configuration information includes at least one of configuration files, data sources, system parameters, and dependent service information.

Preferably, before saving the application package to the storage device, the application package needs to be uploaded, and after the application package is uploaded, the application package needs to be validated, and the content of the validation includes at least whether the application driver file is Existence, whether the application metadata exists, whether the application identifier is used, and whether the configuration items required in the configuration file information meet one of the requirements.

Further, the method also includes a method for stopping the application of the application driver file, specifically including:

Acquire the spring container through the relationship between the application identifier and the spring container;

Use spring boot to destroy the spring container;

Close the class loader used by the container;

Refresh the service resource reference in the spring boot container, and release the execution logic relationship between the externally declared service path and the application package.

Further, the method further includes a method for uninstalling the application driver file, which specifically includes deleting the application package in the storage device after the step of stopping the application is executed.

In the second aspect, the embodiment of the present application also provides a microservice hot deployment system, including:

The application package obtaining unit is used to obtain the application package, and the application package at least includes configuration file information satisfying the spring boot framework service, an application driver file whose content conforms to the spring boot standard and agreed directory rules, and application metadata that can identify the configuration content ;

An application package loading unit, saving the application package to a storage device, and loading the application package in the storage device to a specified file directory;

The class loader creation unit is used to create the class loader of the application package, load the class loader into the class loader collection where the main application program is located, and set the type of its class loader;

The application driver file loading unit is configured to set the application driver file class loader as the class loader created by the class loader for creating the application package, and use the class loader to load the application driver file;

The application metadata association establishment unit, the springboot container obtained after using the spring boot to initialize the application package is associated with the application metadata, and the association comparison table is saved in the program context;

The service resource release unit refreshes the service resource references in the spring boot container, generates service definitions according to the rules of spring external release services, and releases them externally.

In a third aspect, the embodiment of the present application further provides a computer storage medium, where a plurality of instructions are stored in the computer storage medium, and the instructions are suitable for being loaded by a processor to execute the above method steps.

In a fourth aspect, the embodiment of the present application also provides an electronic device, which may include a processor and a memory, where the memory stores a computer program, and the computer program is adapted to be loaded by the processor and execute the above method steps.

The beneficial effects brought by the technical solution provided by some embodiments of the present application at least include: obtaining the application package, saving the application package to a storage device, loading the application package in the storage device to a specified file directory, and creating a class loading of the application package device, and load the class loader into the class loader set where the main application program is located, and at the same time, set the class loader of the application driver file as the class loader created by the class loader for creating the application package, using the The class loader loads the application driver file; finally, use spring boot to initialize the application package, associate the initialized spring boot container with the application metadata, save the associated comparison table in the program context, and refresh the spring boot container Service resource references, according to the rules of spring’s external publishing services, generate service definitions, publish them externally, and provide external access, and then when software upgrades or update configuration applications, it can be released, logged out, and updated services without stopping, thereby avoiding Downtime updates cause the entire application service to be unavailable.

Description of drawings

In order to illustrate the embodiments of the present invention more clearly, the accompanying drawings that need to be used in the descriptions of the embodiments or the prior art will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For Those of ordinary skill in the art can also obtain other drawings based on these drawings without making creative efforts.

Fig. 1 is the flow chart of main steps of the method of the embodiment of the present invention;

Fig. 2 is the detailed flow chart of the method of the embodiment of the present invention;

Fig. 3 is a system block diagram of an embodiment of the present invention;

Fig. 4 is a block diagram of the device structure of the embodiment of the present invention.

The specific implementation manners of the present invention will be described in further detail below in conjunction with the accompanying drawings.

Detailed ways

The present invention will be described in detail below in conjunction with the accompanying drawings. When describing the embodiments of the present invention in detail, for the convenience of explanation, the accompanying drawings showing the structure of the device will not be partially enlarged according to the general scale, and the schematic diagram is only an example, and it should not be limited here. The protection scope of the present invention. It should be noted that the drawings are in simplified form and use inaccurate scales, which are only used to facilitate and clearly assist the purpose of illustrating the embodiments of the present invention.

It should be noted that a microservice hot deployment method provided in this application is generally executed by computer equipment, and correspondingly, a system compatible with communication and interaction of different equipment is generally set in computer equipment.

Various communication client applications can be installed on the computer equipment of this application, such as: video recording applications, video playback applications, voice interaction applications, search applications, instant messaging tools, email clients, social platform software, etc.

Computer equipment can be either hardware or software. When the computer device is hardware, it can be various computer devices with display screens, including but not limited to smartphones, tablets, laptops, and desktops, among others. When the computer equipment is software, it can be installed in the computer equipment listed above. It can be implemented as multiple software or software modules (for example: for providing distributed services), or as a single software or software module, which is not specifically limited here.

When the computer device is hardware, a display device and a camera can also be installed on it, and the display device display can be various devices that can realize display functions, and the camera is used to collect video streams; for example: the display device can be a cathode ray tube display ( cathode ray tube display (CR for short), light-emitting diode display (light-emitting diode display, LED for short), electronic ink screen, liquid crystal display (LCD for short), plasma display panel (plasma display panel, PDP for short), etc. . The user can use the display device on the computer device to view displayed text, pictures, video and other information.

For ease of understanding, a simple example is given below to illustrate the application scenario of the embodiment of the present invention.

Application package A has been deployed in the main application program, in which A1, A2, and A3 are released to the public, and 3 Http services are accessed by system A. After several days of online operation, it is found that the original 3 services are not enough, and 2 additional services need to be added. A service is provided for system B to access. At this time, according to the method of this embodiment, it is only necessary to develop another B application package, which contains two additional services. After the development and testing are completed, install it on the host system and start it. The newly developed The service of the application package is launched successfully.

The general practice in the prior art requires the entire main application program to be repackaged and restarted before the newly added service can be used online. During this process, the A1, A2, and A3 services that have already been launched will also be stopped and cannot be accessed, and the updated service The more frequent, the greater the impact, and the technical solution provided by the embodiment of the present invention can update the service without stopping the main application program.

Specifically, refer to Figure 1 and Figure 2, the microservice hot deployment method, including steps:

S1. Obtain an application package, the application package at least includes resource information such as configuration file information satisfying spring boot framework services, application driver files whose content conforms to spring boot standards and agreed directory rules, and application metadata that can identify configuration content;

In this step, the application package includes configuration file information that satisfies the spring boot framework service as required. The configuration file information may include information such as the service address, name, parameters, and return data of the spring boot framework. These configuration file information are mainly used to provide For external access to search, for example, this information can be used to publish this service as an http service for external use.

In some embodiments, the format of the application driver file is generally springContext.xml, that is, the content of the file is defined by the standard springContext of spring boot, and the directory rules are agreed upon. The purpose of agreeing on the directory rules is to facilitate the main application to read these files according to the determined rules after the next application package is loaded.

In some embodiments, the application package also includes defining application start, stop, and uninstall events. When an application start, stop, or uninstall event is detected, corresponding business processing can be performed after the event is triggered as required.

In some embodiments, the application metadata mainly includes the following elements:

Application name: a meaningful Chinese (English) name displayed on the front end;

Application ID: Globally unique ID, which can determine the unique value of the ID card of the service, which is unique in the entire application;

Application version: conforms to the definition of version number in the industry or within the enterprise;

Service information: basic information on external services, such as service quantity, service description, service type, etc.;

Configuration information: Configuration items required by the application, such as configuration files, data sources, system parameters, dependent services, etc.

After the above resource information is determined, the corresponding application source code can be written and obtained according to the required logic.

In some embodiments, the application source code is built into an application package through standard construction tools, such as maven, ant, gradle, etc. To build the application package, the "application driver file" needs to be placed in the agreed rule directory for subsequent Step loading. The constructed application package is a standard Jar package.

S2, save the application package to the storage device (equivalent to saving to the storage device in the deployment application in Figure 2), and load the application package in the storage device to the specified file directory (equivalent to the last step in the deployment application in Figure 2 : Write the application package to the specified path of the container, and register the application).

Before the application package is stored, the application package needs to be uploaded, and the developed application package can be uploaded through the installation interface of the host where the main application program is located. After uploading the application package, it is also necessary to verify the validity of the application package. The content of the verification mainly includes but is not limited to:

(1) Whether the application driver file exists.

(2) Whether the application metadata exists and the application identifier is not used.

(3) Whether the configuration items required in the configuration information are satisfied.

After the verification is completed, save the application package to the storage device, and load the application package in the storage device to the specified file directory.

S3, create the class loader of the application package, load the class loader into the class loader collection where the main application program is located, and set the type of the class loader;

For ease of understanding, in this step, the specific methods for creating the class loader of the application package include:

Create a UrlClassLoader instance;

Add the application package to the url collection of the instance, set its class loader as the parent class loader, and set the type as the startup class loader to supply the subsequent spring container.

In this step, according to the loaded instances, the application is loaded into the virtual machine where the main application is located, such as creating the java bean instance declared in the driver file, loading the required configuration file information, etc., and the virtual machine can read the declared Service address and other information for external access.

After creating the class loader of the application package, it is also necessary to search for the spring bean-related resources in the application package and configure them. The configured files conform to the XML standard. Refer to "Finding the springbean configuration xml in the application" in the starting application unit in Figure 2.

S4, setting the application driver file class loader as the class loader created by the class loader for creating the application package, and using the class loader to load the application driver file;

S5, use the spring boot initialization application package to obtain the initialized spring boot container, associate the spring boot container with the application metadata, and save the associated comparison table in the program context;

The purpose of the above two steps is to create a program context, see "designate the class loader as the previously created class loader and create xmlapplicationcontext" in the start application unit in Figure 2. The xmlapplicationcontext here is understood as the program context. After the creation is successful, the above comparison table is saved in the program context.

S6. Refresh the service resource reference in the spring boot container, generate a service definition according to the rules of spring's external release service, and release it externally.

In this step, the application startup event is executed, the service resource reference in the spring boot container is refreshed according to the configuration file information, and the externally declared service path is associated with the execution logic of the application package. According to the rules of spring publishing services to the outside world, the definition of the service is generated and released to the outside world.

According to the rules of spring publishing services to the outside world, the definition of the service is generated and released to the outside world. The outside world searches for the corresponding service definition by accessing these addresses, and then executes the corresponding service operation.

In addition, it should be noted that, in some embodiments, the "application metadata" in the application package can also be registered in the current application for presentation and subsequent visualization operations.

In some embodiments, the microservice hot deployment method also includes a method of stopping the application, specifically including:

Get the spring container through the relationship between "application identifier and spring container" saved in the program context;

Execute application stop event;

Use spring boot to destroy the spring container;

Close the class loader ClassLoader used by the container;

Refresh the service resource reference in the spring boot container, and release the execution logic relationship between the externally declared service path and the application package.

In some embodiments, the microservice hot deployment method further includes a method of uninstalling applications, specifically including deleting the application package in the storage device after the stop method is executed.

To sum up, the microservice hot deployment method of this embodiment can not only achieve the goal of updating services without stopping, but also dynamically generate service description documents, and update the service list after the service is released or stopped.

In the second aspect, as shown in FIG. 3, the embodiment of the present application also provides a microservice hot deployment system, and the system includes:

The application package obtaining unit is used to obtain the application package, and the application package at least includes configuration file information satisfying the spring boot framework service, an application driver file whose content conforms to the spring boot standard and agreed directory rules, and application metadata that can identify the configuration content ;

An application package loading unit, saving the application package to a storage device, and loading the application package in the storage device to a specified file directory;

The class loader creation unit is used to create the class loader of the application package, load the class loader into the class loader collection where the main application program is located, and set the type of its class loader;

The application driver file loading unit is configured to set the application driver file class loader as the class loader created by the class loader for creating the application package, and use the class loader to load the application driver file;

The application metadata association establishment unit, the springboot container obtained after using the spring boot to initialize the application package is associated with the application metadata, and the association comparison table is saved in the program context;

The service resource release unit refreshes the service resource references in the spring boot container, generates the definition of the service according to the rules of spring external release services, and releases them externally.

It should be noted that when the system provided by the above embodiment executes the above method, it only uses the division of the above functional modules as an example for illustration. In practical applications, the above function allocation can be completed by different functional modules according to the needs, namely The internal structure of the system is divided into different functional modules to complete all or part of the above functions. In addition, the system and method embodiments provided by the above embodiments belong to the same idea, and the implementation process thereof is detailed in the method embodiments, which will not be repeated here.

The serial numbers of the above embodiments of the present application are for description only, and do not represent the advantages and disadvantages of the embodiments.

The embodiment of the present application also provides a computer storage medium, where a plurality of instructions are stored in the computer storage medium, and the instructions are suitable for being loaded by a processor and executing the above method steps of hot deployment of microservices.

For the specific execution process, reference may be made to the specific description of the embodiment shown in FIG. 1 , and details are not repeated here.

An embodiment of the present application also provides an electronic device, including a processor and a memory, where the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above method for hot deployment of microservices.

Please refer to FIG. 4 , which provides a schematic diagram of the main hardware structure of the microservice hot deployment device according to the embodiment of the present application. As shown in Figure 4,

The microservice hot deployment apparatus 300 may include: at least one processor 301 , at least one network interface 304 , a user interface 303 , a memory 305 , and at least one communication bus 302 .

Wherein, the communication bus 302 is used to realize connection and communication between these components.

Wherein, the user interface 303 may include a touch screen and a camera (Camera).

Wherein, the network interface 304 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).

Wherein, the processor 301 may include one or more processing cores. The processor 301 uses various interfaces and lines to connect various parts in the entire multi-tenant mode data acquisition system 300, and runs or executes instructions, programs, code sets or instruction sets stored in the memory 305, and calls stored in the memory 305. Execute various functions of the multi-tenant mode data acquisition system 300 and process the data. Optionally, the processor 301 may use at least one of Digital Signal Processing (Digital Signal Processing, DSP), Field-Programmable Gate Array (Field-Programmable GateArray, FPGA), and Programmable Logic Array (Programmable Logic Array, PLA). implemented in the form of hardware. The processor 301 may integrate one or a combination of a central processing unit (Central Processing Unit, CPU), an image processor (Graphics Processing Unit, GPU), a modem, and the like. Among them, the CPU mainly handles the operating system, user interface and application programs, etc.; the GPU is used to render and draw the content that needs to be displayed on the display screen; the modem is used to handle wireless communication. It can be understood that the foregoing modem may also not be integrated into the processor 301, but may be realized by a single chip.

Wherein, the memory 305 may include a random access memory (Random Access Memory, RAM), or may include a read-only memory (Read-Only Memory). Optionally, the memory 305 includes a non-transitory computer-readable storage medium. Memory 305 may be used to store instructions, programs, codes, sets of codes, or sets of instructions. The memory 305 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), Instructions and the like for implementing the above method embodiments; the storage data area can store the data and the like involved in the above method embodiments. Optionally, the memory 305 may also be at least one storage device located away from the aforementioned processor 301 . The memory 305 as a computer storage medium may include an operating system, a network communication module, a user interface module and application programs. In the system 300 shown in FIG. 4 , the user interface 303 is mainly used to provide the user with an input interface to obtain the data input by the user; and the processor 301 can be used to call the application program stored in the memory 305, and specifically execute as shown in FIG. 1, the specific process can be referred to as shown in FIG. 1, and will not be repeated here.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be realized through computer programs to instruct related hardware, and the programs can be stored in a computer-readable storage medium along with the main application program When the program is executed, it may include the processes of the embodiments of the above-mentioned methods. Wherein, the storage medium may be a magnetic disk, an optical disk, a read-only memory or a random access memory, and the like.

The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (12)

1. A microservice hot deployment method, characterized in that the method comprises: Obtaining an application package, the application package at least includes configuration file information satisfying the spring boot framework service, an application driver file whose content conforms to the spring boot standard and agreed directory rules, and application metadata that can identify the configuration content; saving the application package to a storage device, and loading the application package in the storage device to a specified file directory; Create the class loader of the application package, load the class loader into the class loader collection where the main application is located, and set the type of its class loader; Setting the application driver file class loader as the class loader created by the class loader for creating the application package, and using the class loader to load the application driver file; Use spring boot to initialize the application package to obtain the spring boot container, associate the spring boot container with application metadata, and save the associated comparison table in the program context; Refresh the service resource reference in the spring boot container, generate the service definition according to the rules of spring's external publishing service, and publish it externally. 2. The method according to claim 1, wherein the configuration file information satisfying the spring boot framework service at least includes the service address, name, parameters, and return data of the spring boot framework. 3. The method according to claim 1, wherein the application package is constructed by a maven, ant or gradle construction tool, and the constructed program package is a jar package. 4. The method according to claim 1, wherein the specific method for creating the class loader of the application package comprises the steps of: Create a UrlClassLoader instance; Add the application package to the url collection of the instance, and set its class loader as the startup class loader. 5. The method according to claim 1, wherein the application driver file is an application driver file in springContext.xml format. 6. The method according to claim 1, wherein the application metadata information includes at least one of application name, application identifier, application version, service information, and configuration information, wherein the service information includes at least One of external service quantity, service description, and service type, and the configuration information includes at least one of configuration files, data sources, system parameters, and dependent service information. 7. The method according to claim 6, wherein before saving the application package to the storage device, the application package needs to be uploaded, and after the application package is uploaded, the application package needs to be Perform verification, and the content of the verification includes at least one of whether the application driver file exists, whether the application metadata exists, whether the application identification is used, and whether the configuration items required in the configuration file information are satisfied. 8. The method according to claim 6, further comprising a method of stopping the application, specifically comprising: Acquire the spring container through the relationship between the application identifier and the spring container; Use spring boot to destroy the spring container; Close the class loader used by the container; Refresh the service resource reference in the spring boot container, and release the execution logic relationship between the externally declared service path and the application package. 9. The method according to claim 8, further comprising a method of uninstalling an application, specifically comprising deleting the application package in the storage device after the steps of claim 8 are performed. 10. A microservice hot deployment system, comprising: The application package obtaining unit is used to obtain the application package, and the application package at least includes configuration file information satisfying the spring boot framework service, an application driver file whose content conforms to the spring boot standard and agreed directory rules, and application metadata that can identify the configuration content ; An application package loading unit, saving the application package to a storage device, and loading the application package in the storage device to a specified file directory; The class loader creation unit is used to create the class loader of the application package, load the class loader into the class loader collection where the main application program is located, and set the type of its class loader; The application driver file loading unit is configured to set the application driver file class loader as the class loader created by the class loader for creating the application package, and use the class loader to load the application driver file; The application metadata association establishment unit is used to establish an association between the spring boot container obtained after the application package is initialized by using spring boot and the application metadata, and save the association comparison table in the program context; The service resource release unit refreshes the service resource references in the spring boot container, generates the definition of the service according to the rules of spring external release services, and releases them externally. 11. A computer storage medium, characterized in that: the computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1-9. 12. An electronic device, characterized in that it comprises a processor and a memory, the memory stores a computer program, and the computer program is adapted to be loaded and executed by the processor as described in any one of claims 1-9 method steps.

Images