Micro-service deployment method and device based on virtual machine sandbox, electronic equipment and storage medium

Abstract

The present disclosure provides a virtual machine sandbox micro-service deployment method, device, electronic equipment and storage medium, the method comprising: obtaining deployment files of a plurality of micro-services, obtaining respective startup entry information of the plurality of micro-services based on the deployment files; for the plurality of micro-services, creating a sandbox environment in a Java virtual machine process; and starting the plurality of micro-services in the sandbox environment in the Java virtual machine process based on the startup entry information. The present disclosure enables deployment of a plurality of micro-services in one virtual machine process.

Description

Technical Field

[0001] This disclosure relates to the field of computer software deployment technology, and in particular to a microservice deployment method, apparatus, electronic device, and storage medium based on a virtual machine sandbox. Background Technology

[0002] In existing technologies, microservice deployment is based on a specific microservice infrastructure framework, with each microservice starting and running as an independent process. It can also be further packaged into container images, with microservice instances isolated via Docker containers, an open-source application container engine. The infrastructure for microservice governance is responsible for a range of functions including hardware resource allocation, microservice deployment, configuration data management, service registration and discovery, monitoring, logging, fault alerting, elastic scaling, and network traffic management.

[0003] However, microservice deployment has the following shortcomings:

[0004] 1. Due to the existence of a large number of small services and complex service interaction relationships, the core of operation becomes service governance, which requires heavy reliance on microservice frameworks and service governance infrastructure. Service governance infrastructure adds a considerable amount of hardware resource overhead to the entire system deployment.

[0005] 2. Each microservice occupies a dedicated process, and each microservice needs to reserve central processing unit (CPU) and memory resources in advance. Due to the isolation characteristics of each service instance, CPU and memory resources cannot be adjusted among microservice instances during runtime. Ultimately, each microservice must reserve CPU and memory resources according to its maximum resource requirements, resulting in low overall utilization of hardware resources.

[0006] 3. When deploying in a private environment, the delivery and deployment team needs to spend a lot of time repeatedly configuring the environment and dependencies for each microservice, resulting in excessively high delivery and deployment costs for the entire system. Summary of the Invention

[0007] This disclosure is made in view of the above-mentioned problems. This disclosure provides a method, apparatus, electronic device, and storage medium for deploying microservices based on a virtual machine (JVM) sandbox.

[0008] According to one aspect of this disclosure, a microservice deployment method based on a virtual machine sandbox is provided, comprising: obtaining deployment files for multiple microservices; obtaining startup entry information for each of the multiple microservices based on the deployment files; creating a sandbox environment for the multiple microservices in a Java Virtual Machine process; and starting the multiple microservices in the sandbox environment in the Java Virtual Machine process based on the startup entry information.

[0009] According to one aspect of this disclosure, the method for deploying microservices based on virtual machine sandboxes includes creating a sandbox environment in a Java Virtual Machine process, wherein multiple sandbox environments are created in a Java Virtual Machine process, and each sandbox environment corresponds to a multiple microservice.

[0010] According to one aspect of the present disclosure, a microservice deployment method based on a virtual machine sandbox further includes: during the startup of multiple microservices, obtaining startup callback methods and termination callback methods registered by multiple microservices; calling the startup callback methods registered by multiple microservices and cyclically checking the running status of multiple microservices; when a microservice is detected to have started successfully, updating the running status of the microservice to startup completed and ending the startup process; and when a timeout occurs and the microservice fails to start, updating the running status of the microservice to startup failed and calling the termination callback methods registered by the microservice.

[0011] According to one aspect of the present disclosure, a microservice deployment method based on a virtual machine sandbox further includes: after starting multiple microservices, cyclically detecting the running status of multiple microservices based on a liveness probe; and if the running status indicates that a microservice has failed or terminated, terminating the thread corresponding to the microservice and shutting down the sandbox environment corresponding to the microservice.

[0012] Furthermore, according to another aspect of this disclosure, a microservice deployment apparatus based on a virtual machine sandbox is provided, comprising: a deployment file acquisition unit configured to acquire deployment files for multiple microservices and, based on the deployment files, acquire startup entry information for each of the multiple microservices; a sandbox environment creation unit configured to create a sandbox environment for the multiple microservices in a Java Virtual Machine process; and a microservice startup unit configured to start the multiple microservices in the sandbox environment within a Java Virtual Machine process based on the startup entry information.

[0013] Furthermore, according to another aspect of this disclosure, the sandbox-based microservice deployment apparatus further configures the sandbox environment creation unit to create multiple sandbox environments within a Java Virtual Machine process, with each sandbox environment corresponding to a specific microservice.

[0014] Furthermore, according to another aspect of the present disclosure, the microservice deployment apparatus based on a virtual machine sandbox, the microservice startup unit is further configured to: during the startup of multiple microservices, obtain multiple startup callback methods and registered termination callback methods registered by the microservices; call the multiple startup callback methods registered by the microservices to continuously detect the running status of the multiple microservices; when the microservice startup is detected as successful, update the microservice running status to startup completed and end the startup process; and when the detection times out and the microservice startup fails, update the microservice running status to startup failed and call the microservice registered termination callback method.

[0015] Furthermore, the microservice deployment apparatus based on a virtual machine sandbox according to another aspect of this disclosure further includes a runtime status detection unit configured to cyclically detect the runtime status of multiple microservices based on a liveness probe after the process of starting multiple microservices; and a microservice termination unit configured to terminate the thread corresponding to the microservice and shut down the sandbox environment corresponding to the microservice when the runtime status indicates that the microservice has failed or terminated.

[0016] According to another aspect of this disclosure, an electronic device is provided, comprising: a memory for storing computer-readable instructions; and a processor for executing the computer-readable instructions, causing the electronic device to perform the microservice deployment method based on a virtual machine sandbox as described above.

[0017] According to another aspect of this disclosure, a storage medium is provided for storing computer-readable instructions that, when executed by a processor, cause the processor to perform the microservice deployment method based on a virtual machine sandbox as described above.

[0018] As will be described in detail below, the JVM sandbox-based microservice deployment method, apparatus, electronic device, and storage medium according to embodiments of this disclosure directly use deployment artifacts including multiple microservices, which are the same as those used in independent process deployment of microservices. No code modification is required, and no dedicated deployment artifact format needs to be generated. The same set of code and artifact files can be used in both independent process deployment and shared process deployment, making it more flexible and convenient. Furthermore, the JVM sandbox microservice system has no constraints on the network services provided by the microservices, does not care whether the microservice application provides network services to the outside world, and does not care about the network protocol or network port used. The microservice application does not need to be aware of the existence of the JVM sandbox environment. Microservices can dynamically add network service ports and protocols. Furthermore, using a JVM sandbox-based microservice deployment method supports dynamic deployment and termination of microservices. Further, by using a JVM agent and Aspect-Oriented Programming (AOP) technology to obtain the listener programs (such as ServletContextListener) and termination mechanisms (such as JVM shutdown hooks) registered in the microservice code, the registered callback methods are executed when the microservice starts and terminates, ensuring the compatibility of the microservice execution flow. Furthermore, the scheme provided in this disclosure for deploying multiple microservice applications in the same process facilitates one-click deployment of microservice application systems. The microservice sandbox system program, microservice deployment artifacts, and configuration files are packaged and uploaded together; a single command can start the microservice sandbox and start the microservices one by one according to the configuration files, achieving one-click deployment.

[0019] It should be understood that both the foregoing general description and the following detailed description are exemplary and intended to provide further illustration of the claimed technology. Attached Figure Description

[0020] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of the embodiments thereof in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the embodiments of this disclosure to explain the disclosure and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.

[0021] Figure 1 This is a schematic diagram of a JVM sandbox microservice system according to an embodiment of the present disclosure.

[0022] Figure 2 This diagram illustrates a microservice deployment method based on a JVM sandbox according to an embodiment of this disclosure.

[0023] Figure 3 This is a flowchart illustrating a method for dynamically deploying microservices according to an embodiment of the present disclosure.

[0024] Figure 4 This is a functional block diagram illustrating a JVM sandbox-based microservice deployment apparatus according to an embodiment of the present disclosure.

[0025] Figure 5 This is a hardware block diagram illustrating an electronic device according to an embodiment of the present disclosure.

[0026] Figure 6 This is a schematic diagram illustrating a storage medium according to an embodiment of the present disclosure. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of this disclosure more apparent, exemplary embodiments according to this disclosure will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this disclosure, and not all embodiments of this disclosure. It should be understood that this disclosure is not limited to the exemplary embodiments described herein.

[0028] First, refer to Figure 1 and Figure 2 This invention describes a microservice deployment method based on a JVM sandbox according to embodiments of the present disclosure. Figure 1 This is a schematic diagram of a JVM sandbox microservice system according to an embodiment of the present disclosure.

[0029] like Figure 1As shown, the JVM sandbox microservice system according to embodiments of this disclosure includes modules such as an application launcher, an application liveness probe, an application uninstaller, an application management console, and an application sandbox. Each microservice instance generates a sandbox responsible for microservice status tracking and management.

[0030] in:

[0031] The App Launcher module is used to parse microservice artifacts and configurations and guide the startup of microservices.

[0032] The App Liveness Probe module is used to detect the running status of microservices and determine whether they are alive. Depending on the configuration, it supports multiple detection methods, including Transmission Control Protocol (TCP) connections, Hypertext Transfer Protocol (HTTP) interface requests, and method calls. It can also release resources promptly in the event of an application crash.

[0033] The App Unloader module is used to terminate microservices and release the resources they occupy.

[0034] The Manage Console module is used to manage the microservices running in the sandbox system, including querying the list and status of deployed microservices, viewing logs, terminating running microservice instances, and starting new microservice instances.

[0035] The App Sandbox module is used to maintain the metadata of microservice instances, which includes information such as the operation records of deployed microservice instances, deployment logs, identifier ID, class loader, thread group name, deployment artifact directory, and configuration files.

[0036] This disclosure provides a microservice deployment method based on a JVM sandbox. A sandbox is a technology in which software runs in a restricted operating system environment. In the field of computer security, a sandbox is a mechanism for securely running programs, often used to execute untrusted programs. Malicious code in untrusted programs will have its impact on the system confined within the sandbox and will not affect other parts of the system. Sandbox technology achieves isolation by strictly limiting the use of system resources by untrusted programs according to certain security policies.

[0037] JVM stands for Java Virtual Machine. It is a specification for computing devices. It is a virtual computer that is implemented by simulating various computer functions on an actual computer.

[0038] Reference Figure 2 Describe in detail the microservice deployment method based on JVM sandbox.

[0039] like Figure 2 As shown, the microservice deployment method based on JVM sandbox according to an embodiment of this disclosure includes the following steps:

[0040] In step S201, the deployment files of multiple microservices are obtained, and based on the deployment files, the startup entry information of each of the multiple microservices is obtained.

[0041] In the embodiments of this disclosure, multiple microservices are deployed in a JVM sandbox microservice system, and these microservices are loaded within the system. Deployment files for these microservices are obtained from the JVM sandbox microservice system, and the startup entry point information for each microservice is obtained using these deployment files. The deployment files for the microservices include deployment artifacts, specifically, fat JAR files, etc.

[0042] Specifically, in the embodiments of this disclosure, a microservice deployment artifact fatJar file is generated based on the Spring Boot framework, the microservice deployment artifact fatJar file is decompressed, the deployment description file MANIFEST.MF is obtained, and the microservice startup entry information (entry class) is read from the deployment description file.

[0043] In step S202, a sandbox environment is created in a Java Virtual Machine process for multiple microservices.

[0044] In the embodiments disclosed herein, multiple sandbox environments are created within a single Java Virtual Machine process, with each sandbox environment corresponding to a specific microservice.

[0045] In step S203, based on the startup entry information, multiple microservices are started in a sandbox environment within a Java Virtual Machine process.

[0046] In the embodiments of this disclosure, a corresponding sandbox is created for each microservice. This sandbox is used to track and manage the status of each microservice. A microservice instance ID, class loader, and thread group are configured for each microservice, and threads for each microservice are started. This enables the deployment of multiple microservices within the same JVM process. Deploying multiple microservice instances within a single JVM process saves server memory and CPU resources.

[0047] ID is an abbreviation for Identity, which means identity, identifier, etc. In the computer field, ID is usually used as an identifier to identify a certain data or object, and is used to uniquely identify a piece of data or a user in a database.

[0048] The above describes a microservice deployment method based on a virtual machine sandbox. The following further describes a method for dynamically deploying microservices according to embodiments of this disclosure.

[0049] like Figure 3 The flowchart shown is a method for dynamically deploying microservices according to an embodiment of this disclosure.

[0050] This dynamic deployment method for microservices is applied during and after the process of starting multiple microservices.

[0051] The method includes the following steps when starting multiple microservices:

[0052] In step S301, the startup callback method and the termination callback method of the registration of multiple microservices are obtained.

[0053] In the embodiments of this disclosure, by using aspect-oriented programming (AOP), multiple startup callback methods and termination callback methods registered by microservices are obtained when loading a microservice application.

[0054] In step S302, the startup callback methods of multiple microservices are called to continuously monitor the running status of multiple microservices.

[0055] In step S303, it is determined whether the microservice has started successfully.

[0056] If a positive result is obtained in step S303, proceed to step S305.

[0057] In step S305, the microservice running status is updated to startup complete.

[0058] Further, in step S306, the startup process is terminated.

[0059] If it is determined in step S303 that the microservice startup has failed, then proceed to step S304.

[0060] In step S304, the microservice running status is updated to "startup failed," and the termination callback method registered by the microservice is invoked. Then, proceed to step S307.

[0061] Further, in step S307, the thread corresponding to the microservice is terminated, and the sandbox environment corresponding to the microservice is shut down. Further, after step S307, the process includes cleaning up other applications that are difficult to clean up automatically, unregistering the class loader of the microservice instance from the virtual machine sandbox system, and ending the process. Applications that are difficult to clean up automatically refer to bugs that exist in the JVM program during runtime. These bugs are difficult to automatically remove during JVM program execution and require manual handling. In the microservice deployment method, these bugs need to be removed to ensure better JVM program operation.

[0062] After starting multiple microservices, a liveness probe is used to continuously monitor the running status of each microservice. If a microservice fails or terminates, the thread corresponding to that microservice is terminated, and the sandbox environment for that microservice is shut down. This process continues until all microservices terminate, at which point all threads corresponding to those microservices are shut down, the sandbox environment for each microservice is closed, and a Java Virtual Machine process is terminated.

[0063] That is, the running status of multiple microservices is monitored cyclically based on the survival probe. If the running status indicates that the microservice has failed or terminated, the thread corresponding to the microservice is terminated and the sandbox environment corresponding to the microservice is shut down.

[0064] The JVM sandbox microservice system and the JVM sandbox-based microservice deployment method according to embodiments of this disclosure have been described above. The JVM sandbox-based microservice deployment apparatus will be further described below. Figure 4 This is a functional block diagram illustrating a JVM sandbox-based microservice deployment device according to an embodiment of the present disclosure.

[0065] like Figure 4 As shown, the microservice deployment apparatus 400 based on a virtual machine sandbox according to an embodiment of this disclosure includes a deployment file acquisition unit 401, a sandbox environment creation unit 402, a microservice startup unit 403, a running status detection unit 404, and a microservice termination unit 405. Those skilled in the art will readily understand that these unit modules can be implemented individually in hardware, individually in software, or in combination thereof in various ways, and this disclosure is not limited to any one of them.

[0066] Specifically, the deployment file acquisition unit 401 is configured to acquire deployment files for multiple microservices, and based on the deployment files, acquire the startup entry information for each of the multiple microservices.

[0067] Specifically, the sandbox environment creation unit 402 is configured to create sandbox environments within a single Java Virtual Machine process for multiple microservices.

[0068] Specifically, the microservice startup unit 403 is configured to start multiple microservices in a sandbox environment within a Java Virtual Machine process based on startup entry information.

[0069] Specifically, the sandbox environment creation unit 402 is further configured to create multiple sandbox environments within a single Java Virtual Machine process, with each sandbox environment corresponding one-to-one with a microservice.

[0070] Specifically, the microservice startup unit 403 is further configured to: obtain the startup callback methods and termination callback methods registered by multiple microservices during the startup of multiple microservices; call the startup callback methods registered by multiple microservices and continuously check the running status of multiple microservices; when the microservice startup is detected as successful, update the running status of the microservice to startup completed and end the startup process; and when the detection times out and the microservice startup fails, update the running status of the microservice to startup failed and call the termination callback method registered by the microservice.

[0071] Specifically, the status detection unit 404 is configured to cyclically detect the running status of multiple microservices based on a liveness probe after the process of starting multiple microservices.

[0072] Specifically, the microservice termination unit 405 is configured to terminate the thread corresponding to the microservice and shut down the sandbox environment corresponding to the microservice when the running status indicates that the microservice has failed or terminated.

[0073] Figure 5 This is a hardware block diagram illustrating an electronic device 500 according to an embodiment of the present disclosure. The electronic device according to an embodiment of the present disclosure includes at least a processor and a memory for storing computer-readable instructions. When the computer-readable instructions are loaded and executed by the processor, the processor performs the JVM sandbox-based microservice deployment method as described above.

[0074] Figure 5 The illustrated electronic device 500 specifically includes a central processing unit (CPU) 501, a graphics processing unit (GPU) 502, and a main memory 503. These units are interconnected via a bus 504. The CPU 501 and / or GPU 502 can function as the aforementioned processor, and the main memory 503 can function as the aforementioned memory storing computer-readable instructions. Furthermore, the electronic device 500 may also include a communication unit 505, a storage unit 505, an output unit 507, an input unit 508, and an external device 509, all of which are also connected to the bus 504.

[0075] Figure 6 This is a schematic diagram illustrating a storage medium according to an embodiment of the present disclosure. Figure 6As shown, the storage medium 600 according to an embodiment of the present disclosure stores computer-readable instructions 601 thereon. When the computer-readable instructions 601 are executed by a processor, the JVM sandbox-based microservice deployment method according to an embodiment of the present disclosure, as described with reference to the above figures, is performed. The computer-readable storage medium includes, but is not limited to, volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, optical disk, magnetic disk, etc.

[0076] The above description, with reference to the accompanying drawings, outlines a JVM sandbox-based microservice deployment method, apparatus, electronic device, and storage medium according to embodiments of this disclosure. It directly uses Spring Boot fat JAR deployment artifacts, identical to those used in independent process deployments of microservices. No code modification or generation of a dedicated deployment artifact format is required. This allows for flexible and convenient deployment using the same codebase and artifact files, enabling deployment in both independent and shared processes. The JVM sandbox microservice system imposes no constraints on the network services provided by the microservices, disregarding whether the microservice application provides network services, the network protocol used, or the network port used. The microservice application is also unaware of the JVM sandbox environment. Microservices can dynamically add network service ports and protocols. The JVM sandbox-based microservice deployment method supports dynamic deployment and termination of microservices. By using JVMagent and AOP technologies to obtain the ServletContextListener and JVM shutdown hook registered in the microservice code, the registered callback methods are executed during microservice startup and termination, ensuring compatibility of the microservice execution flow. The scheme for deploying multiple microservice applications in the same process provided by this disclosure facilitates one-click deployment of microservice application systems. The microservice sandbox system program, microservice deployment artifacts, and configuration files are packaged and uploaded together. A single command can start the microservice sandbox and start microservices one by one according to the configuration files, achieving one-click deployment.

[0077] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0078] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.

Claims

1. A microservice deployment method based on a virtual machine sandbox, characterized in that, include: Obtain deployment files for multiple microservices; based on the deployment files, obtain the entry class for each of the multiple microservices; the deployment files include deployment artifacts of the microservices, and the deployment artifacts include fat JAR files. For the aforementioned microservices, a sandbox environment is created within a single Java Virtual Machine process; as well as Based on the entry class, the multiple microservices are started in the sandbox environment within the Java Virtual Machine process.

2. The microservice deployment method based on virtual machine sandbox according to claim 1, characterized in that, Creating a sandbox environment within a Java Virtual Machine process includes: Multiple sandbox environments are created within a single Java Virtual Machine process, and each sandbox environment corresponds one-to-one with a single microservice.

3. The microservice deployment method based on virtual machine sandbox according to claim 1, characterized in that, The method further includes: During the process of starting the multiple microservices, the startup callback method and the termination callback method registered by the multiple microservices are obtained; The startup callback methods registered by the multiple microservices are invoked to continuously monitor the running status of the multiple microservices; When the microservice startup is detected as successful, the microservice running status is updated to "startup complete," and the startup process ends; and When the detection times out and the microservice fails to start, update the microservice's running status to "startup failed" and call the termination callback method registered by the microservice.

4. The microservice deployment method based on a virtual machine sandbox according to claim 3, characterized in that, The method further includes: After starting the multiple microservices, the running status of the multiple microservices is cyclically monitored based on liveness probes; and If the running status indicates that the microservice has failed or terminated, the thread corresponding to the microservice is terminated, and the sandbox environment corresponding to the microservice is shut down.

5. A microservice deployment device based on a virtual machine sandbox, characterized in that, include: The deployment file acquisition unit is configured to acquire deployment files of multiple microservices, and based on the deployment files, acquire the entry class of each of the multiple microservices. The deployment files include the deployment artifacts of the microservices, and the deployment artifacts include fatJar files. The sandbox environment creation unit is configured to create a sandbox environment within a Java Virtual Machine process for the multiple microservices. The microservice startup unit is configured to start the multiple microservices in the sandbox environment within the Java Virtual Machine process based on the entry class.

6. The microservice deployment device based on a virtual machine sandbox according to claim 5, characterized in that, The sandbox environment creation unit is further configured as follows: Multiple sandbox environments are created within a single Java Virtual Machine process, and each sandbox environment corresponds one-to-one with a single microservice.

7. The microservice deployment device based on a virtual machine sandbox according to claim 5, characterized in that, The microservice startup unit is further configured as follows: During the process of starting the multiple microservices, the startup callback method and the termination callback method registered by the multiple microservices are obtained; The startup callback methods registered by the multiple microservices are invoked to continuously monitor the running status of the multiple microservices; When the microservice is detected to have started successfully, update the microservice running status to "startup complete" and end the startup process. as well as When the detection times out and the microservice fails to start, update the microservice's running status to "startup failed" and call the termination callback method registered by the microservice.

8. The microservice deployment device based on a virtual machine sandbox according to claim 7, characterized in that, Also includes: The running status detection unit is configured to cyclically detect the running status of the multiple microservices based on the liveness probe after the process of starting the multiple microservices; as well as The microservice termination unit is configured to terminate the thread corresponding to the microservice and shut down the sandbox environment corresponding to the microservice when the running status indicates that the microservice has failed or terminated.

9. An electronic device, characterized in that, include: Memory, used to store computer-readable instructions; as well as A processor for executing the computer-readable instructions, causing the electronic device to perform the microservice deployment method based on a virtual machine sandbox as described in any one of claims 1 to 4.

10. A storage medium for storing computer-readable instructions, characterized in that, When the computer-readable instructions are executed by a processor, the processor performs the microservice deployment method based on a virtual machine sandbox as described in any one of claims 1 to 4.

Images