Digital archive micro-service system based on mobile target defense

Abstract

The invention discloses a digital archive micro-service system based on mobile target defense, and the system comprises a digital archive workflow generator which automatically designs a workflow model meeting the demands of a user according to a submitted application; the micro-service application set is used for storing the micro-service application set corresponding to the digital archive management whole process; the heterogeneous running resource pool is used for storing virtual machines corresponding to the diversified operating systems; the mobile target defense scheduler schedules heterogeneous operation resources at a certain probability for different links of the digital archive workflow based on a mobile target defense thought to support service provision; the micro-service assembler assembles a micro-service application into the selected heterogeneous operation resources according to the output workflow model, and instantiation of a micro-service function is achieved; and the digital archive workflow monitor tracks the full-process operation of the archive workflow, and discovers and disposes abnormal micro-service applications in time. According to the invention, the security of the digital archive information system is improved.

Description

Technical Field

[0001] The present invention relates to the field of network security technology, and in particular to a digital archive microservice system based on mobile target defense. Background Art

[0002] Traditional digital archival information systems based on monolithic architectures are unable to meet the archival management needs for high-efficiency, high-performance, multi-functional, and scalable digital archival information systems due to shortcomings such as poor application scalability, high software module coupling, high system operation and maintenance costs, low deployment efficiency, long new feature launch cycles, and slow iterative updates. With the rapid development of cloud computing and container technologies, microservices architectures, with their advantages of service customization and application modularity, are gradually replacing the monolithic architectures of traditional digital archival information systems and becoming the preferred choice for digital archival information system developers.

[0003] The digital archive information system based on microservice architecture has the following advantages: First, the service coupling is low. Services such as archive screening, archive statistics, and archive retrieval are all implemented based on independent software modules, and each service is deployed and run independently; second, resource utilization is high. The dynamic scaling mechanism of microservices can achieve flexible adaptation of the software system and the hardware environment. When service requests are intensive, the information system performance is improved by dynamically expanding computing resources. When service requests are sparse, costs are saved by dynamically releasing computing resources; third, the system is easy to operate and maintain. Due to the high degree of decoupling of service applications, operation and maintenance personnel can quickly locate abnormal service modules when the system fails, and repair and update the abnormal modules without affecting other modules; fourth, it is easy to expand functions. When archive management personnel have new functional requirements for the information system, they only need to develop new functional modules and register them in the system to complete the launch of new functions. There is no need to modify the original system code, which significantly shortens the launch cycle of new functions.

[0004] However, while the "breaking down the whole into parts" approach of microservices architecture enables digital archival information systems to provide high-quality services, it also poses serious security threats. Service interfaces are often vulnerable points in information systems, and the microservices-based transformation of digital archival information systems is accompanied by a significant increase in the number of service interfaces. Frequent data exchange between microservices through these interfaces aggregates service functionality, expanding the attack surface and dramatically increasing the risk of infiltration and intrusion facing information systems. Existing solutions are generally based on passive defense methods based on rules and feature matching, such as intrusion detection and firewalls. These solutions rely heavily on prior knowledge and are ineffective against new types of network attacks with unknown features. Summary of the Invention

[0005] In response to the above problems, the present invention provides a digital archive microservice system based on mobile target defense. By implanting inherent security attributes such as dynamicity and heterogeneity into the digital archive information system based on the microservice architecture, it realizes active defense capabilities against network attacks and improves the security of the digital archive information system.

[0006] In order to achieve the above object, the present invention adopts the following technical solutions:

[0007] A digital archive microservice system based on mobile target defense, comprising: a digital archive workflow generator, a microservice application set, a heterogeneous operation resource pool, a mobile target defense scheduler, a microservice assembler and a digital archive workflow monitor;

[0008] The digital archive workflow generator is used to automatically design a workflow model that meets user needs based on the application submitted by the user;

[0009] The microservice application set is used to store the microservice application set corresponding to the entire digital archive management process in a mirrored form;

[0010] The heterogeneous operation resource pool is used to store virtual machines corresponding to diverse operating systems in the form of images;

[0011] The mobile target defense scheduler is used to schedule heterogeneous operating resources at different stages of the digital archive workflow with a certain probability to support service provision based on the mobile target defense concept;

[0012] The microservice assembler is used to assemble the microservice application into the heterogeneous running resources selected by the mobile target defense scheduler according to the workflow model output by the digital archive workflow generator, thereby realizing the instantiation of the microservice function;

[0013] The digital archive workflow monitor is used to track the entire process of the archive workflow and promptly discover and handle abnormal microservice applications.

[0014] Furthermore, the digital archive workflow generator is specifically used to:

[0015] Obtain digital archive operation requests; parse the operation requests and extract user needs; based on the extracted user needs, select microservice applications that can meet the user needs from a set of microservice applications; parse the data dependencies of the selected microservice applications and calculate the optimal microservice provision sequence; use the output microservice applications as nodes and the output microservice provision sequence as directed edges to model the user requests in a directed acyclic graph to obtain a workflow model that meets the user needs, and store the workflow model in an XML format file.

[0016] Furthermore, the microservice application set is constructed in the following manner:

[0017] Complete the development of microservice software modules for digital archive management; deploy the microservice software modules in containers and store them in mirror mode.

[0018] Furthermore, the mobile target defense scheduler is specifically used to:

[0019] Obtain vulnerability data online through common vulnerability enumeration, and count the corresponding vulnerabilities based on the operating system types in the heterogeneous running resource pool;

[0020] Convert the number of vulnerabilities in the operating system into a first scheduling probability, select the operating environment type corresponding to the initial microservice based on the first scheduling probability, select the corresponding system image from the image library and instantiate it as the operating environment of the initial microservice;

[0021] The number of common vulnerabilities between the operating system to be scheduled and the operating environment type corresponding to the initial microservice is converted into a second scheduling probability. The operating environment type corresponding to the non-initial microservice is selected according to the second scheduling probability. The corresponding system image is selected from the image library and instantiated as the operating environment of the non-initial microservice.

[0022] Furthermore, the first scheduling probability is calculated as follows:

[0023]

[0024] where p i represents the first scheduling probability corresponding to the i-th type of operating system, o i represents the i-th type of operating system, v(o i ) represents the number of vulnerabilities of the i-th operating system.

[0025] Furthermore, the second scheduling probability is calculated as follows:

[0026]

[0027] where p′ i represents the second scheduling probability corresponding to the i-th type of operating system, o x The operating environment corresponding to the initial microservice of the archive workflow is the operating system, v(o x ,o i ) represents the operating system to be scheduled o i With o x The number of common mode vulnerabilities between

[0028] Furthermore, the microservice assembler is specifically used to:

[0029] When a microservice automatic assembly command is received, the container file where the microservice application is deployed is copied to the heterogeneous operating environment through an automated script; the container is instantiated through console commands in the operating environment; the instantiated container automatically starts the microservice process; and the fixed service port is monitored to determine whether the assembly of the microservice application is completed. If it is running normally, the process is terminated; otherwise, the process is re-executed.

[0030] Furthermore, the digital archive workflow monitor is specifically used to:

[0031] Read the XML format file generated by the digital archive workflow generator, obtain the archive workflow model, and obtain the microservice information that the archive workflow is about to execute;

[0032] Check the fixed service port to determine whether the microservice application is running normally. If it is running normally, wait for the microservice application to complete the instruction. Otherwise, re-automatically assemble the service.

[0033] After receiving the microservice application completion instruction, the service quality is evaluated. If the quality meets the requirements, the microservice information that the archival workflow is about to execute is iteratively obtained until the archival workflow execution is completed; if the quality does not meet the requirements, the execution of the archival workflow is terminated, and the microservice information that does not meet the service quality is reported to the system administrator.

[0034] Furthermore, the system's response process includes:

[0035] Get digital archive operation request;

[0036] Activate the digital archive workflow generator to complete the archive workflow modeling;

[0037] The digital archive workflow monitor loads the archive workflow model and selects the corresponding microservice application from the microservice application set according to the workflow running stage;

[0038] Activate the mobile target defense scheduler and select the operating environment type of the microservice application to be executed;

[0039] Activate the microservice assembler to complete the instantiation of the microservice application;

[0040] Send the dependent data to the corresponding microservice application interface to complete the microservice response;

[0041] The iteration selects the corresponding microservice application from the microservice application set according to the workflow running stage until the archive workflow execution is completed.

[0042] Compared with the prior art, the present invention has the following beneficial effects:

[0043] The present invention provides a digital archive microservice system based on mobile target defense. By implanting inherent security attributes such as dynamicity and heterogeneity into the digital archive information system based on the microservice architecture, it realizes active defense capability against network attacks and improves the security of the digital archive information system. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 An architectural diagram of a digital archive microservice system based on mobile target defense is provided for an embodiment of the present invention;

[0045] Figure 2 A digital archive workflow modeling flow chart provided by an embodiment of the present invention;

[0046] Figure 3 A flow chart of heterogeneous resource scheduling based on mobile target defense provided by an embodiment of the present invention;

[0047] Figure 4 A flowchart of microservice automatic assembly for heterogeneous operating environments provided by an embodiment of the present invention;

[0048] Figure 5 A flowchart of archive workflow operation monitoring provided by an embodiment of the present invention;

[0049] Figure 6 A response flow chart of a digital archive microservice system based on mobile target defense provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0050] The present invention will be further explained below with reference to the accompanying drawings and specific embodiments:

[0051] Example 1

[0052] like Figure 1 As shown, a digital archive microservice system based on mobile target defense is provided, which includes: 1) a digital archive workflow generator, which automatically designs a workflow model that meets user needs based on the application submitted by the user; 2) a microservice application set, which stores the full-process application set of digital archive management, and each function is designed and implemented in the form of a single software module; 3) a heterogeneous operation resource pool, which stores virtual machines corresponding to diverse operating systems in the form of images; 4) a mobile target defense scheduler, which, based on the mobile target defense idea, schedules heterogeneous operation resources with a certain probability for different links of the digital archive workflow to support the provision of services; 5) a microservice assembler, which assembles microservice applications into the heterogeneous operation resources selected by the scheduler according to the workflow model output by the digital archive workflow generator, thereby realizing the instantiation of microservice functions; 6) a digital archive workflow monitor, which is responsible for tracking the full-process operation of the archive workflow and promptly discovering and handling abnormal microservice applications.

[0053] The components of the system are described in detail as follows:

[0054] (1) Digital archive workflow generator. In digital archive management, user requests to the information system must go through a series of processing steps to complete the response to the request. In order to facilitate the supervision and tracking of each step, the digital archive workflow generator uses a directed acyclic graph (DAG) to model user needs based on the application submitted by the user. Each node in the DAG represents the microservice required to meet the user's needs, and each edge represents the dependency data between microservices. Each edge has a direction attribute, where the source end of the edge represents the producer of the dependency data, and the end end of the edge represents the consumer of the dependency data. The formed DAG model is stored in an XML format file.

[0055] In summary, the digital archive workflow generator is specifically used to:

[0056] Obtain digital archive operation requests; parse the operation requests and extract user needs; based on the extracted user needs, select microservice applications that can meet the user needs from a set of microservice applications; parse the data dependencies of the selected microservice applications and calculate the optimal microservice provision sequence; use the output microservice applications as nodes and the output microservice provision sequence as directed edges to model the user requests in a directed acyclic graph to obtain a workflow model that meets the user needs, and store the workflow model in an XML format file.

[0057] (2) Microservice application collection. The service functions of the digital archive information system are disassembled and divided into services such as archive collection, archive retrieval, archive association, archive organization, archive screening, archive statistics, archive maintenance, archive backup, archive review, archive portal, archive destruction, authority management, log management, and report management. Corresponding microservice software modules are developed as providers of various services. In order to achieve rapid deployment of microservice functional modules and adapt to the underlying heterogeneous operating environment, each microservice software module is deployed in an independent container, and the deployed containers are packaged into images and stored in the image library for future use.

[0058] (3) Heterogeneous operation resource pool. Build virtual machines based on diverse operating systems such as OpenBSD, NetBSD, FreeBSD, Windows 7, Windows 8, Windows 10, Ubuntu, Debian, Redhat, Solaris, and OpenSolaris, and save the virtual machines as images in the image library. When the system receives a service request, it quickly forms a heterogeneous operation resource pool by instantiating the image to support the operation of the microservice software module.

[0059] (4) Mobile Target Defense Scheduler. The mobile target defense scheduler is the core of the solution provided by the present invention and the source of power for the system to provide active defense capabilities. Considering that many current penetration attacks against service applications are caused by vulnerabilities in the operating environment, the mobile target defense scheduler will automatically obtain the latest vulnerability data from the Common Vulnerability Enumeration (CVE) before each trigger, and count the number of vulnerabilities in operating systems such as OpenBSD, NetBSD, FreeBSD, Windows 7, Windows 8, Windows 10, Ubuntu, Debian, Redhat, Solaris, and OpenSolaris, as well as the number of common vulnerabilities between operating systems. The number of vulnerabilities in the operating system is used to measure the security of the operating system itself, and the number of common vulnerabilities between operating systems is used to measure the heterogeneity between operating systems.

[0060] For the initial microservice of the archive workflow, the moving target defense scheduler converts the number of vulnerabilities of the operating system into the first scheduling probability, as shown in Equation (1).

[0061]

[0062] Among them, i represents the i-th type of operating system, v(o i ) represents the number of vulnerabilities in the i-th type of operating system, p i represents the first scheduling probability (i.e., selection probability) of the i-th type of operating system. Formula (1) shows that while ensuring the randomness of the operating environment, the moving target defense scheduler will prioritize providing a more secure operating system as its operating environment for the initial microservice of the archive workflow.

[0063] Assume that the operating environment corresponding to the initial microservice of the archive workflow is the operating system o x , then for other microservices after the initial microservice, the mobile target defense scheduler will schedule the operating system o i With o x The number of common mode v(o x,o i ) is converted into the second scheduling probability p′ i , as shown in formula (2).

[0064]

[0065] Formula (2) shows that while ensuring the randomness of the operating environment, the mobile target defense scheduler will prioritize providing the operating system with the greatest heterogeneity with the current environment as the operating environment for the non-initial microservices of the archive workflow, thereby reducing the risk of adjacent microservices being chained by attacks.

[0066] In summary, the mobile target defense scheduler is specifically used to:

[0067] Obtain vulnerability data online through common vulnerability enumeration, and count the corresponding vulnerabilities based on the operating system types in the heterogeneous running resource pool;

[0068] Convert the number of vulnerabilities in the operating system into a first scheduling probability, select the operating environment type corresponding to the initial microservice based on the first scheduling probability, select the corresponding system image from the image library and instantiate it as the operating environment of the initial microservice;

[0069] The number of common vulnerabilities between the operating system to be scheduled and the operating environment type corresponding to the initial microservice is converted into a second scheduling probability. The operating environment type corresponding to the non-initial microservice is selected according to the second scheduling probability. The corresponding system image is selected from the image library and instantiated as the operating environment of the non-initial microservice.

[0070] (5) Microservice assembler. The role of the microservice assembler is to instantiate microservices. Specifically, it deploys and starts the software module that carries the microservice in the operating environment through automated scripts. Since the operating environment selected by the mobile target defense scheduler is random and heterogeneous, in order to shield the impact of the differences in the operating environment on the deployment of the microservice software module, the differences in the underlying environment are isolated through container technology, reducing the difficulty of automated deployment of microservice software modules in heterogeneous environments.

[0071] In summary, the microservice assembler is specifically used to:

[0072] When a microservice automatic assembly command is received, the container file where the microservice application is deployed is copied to the heterogeneous operating environment through an automated script; the container is instantiated through console commands in the operating environment; the instantiated container automatically starts the microservice process; and the fixed service port is monitored to determine whether the assembly of the microservice application is completed. If it is running normally, the process is terminated; otherwise, the process is re-executed.

[0073] (6) Digital Archives Workflow Monitor. The Digital Archives Workflow Monitor is responsible for tracking the entire process of the archives workflow. When the monitor detects that a task in the workflow has been completed, it will load the archives workflow DAG model and select the microservice application required for the next task based on the model. At the same time, it will activate the mobile target defense scheduler to select a suitable operating environment for the next microservice. After completing the above work, the monitor will activate the microservice assembler, which will complete the automated deployment and operation of the microservice application in the operating environment. In addition, the digital archives workflow monitor is also responsible for inspecting and evaluating the quality of microservice provision in each link, and promptly discovering and handling abnormal microservice modules.

[0074] In summary, the digital archive workflow monitor is specifically used to:

[0075] Read the XML format file generated by the digital archive workflow generator, obtain the archive workflow model, and obtain the microservice information that the archive workflow is about to execute;

[0076] Check the fixed service port to determine whether the microservice application is running normally. If it is running normally, wait for the microservice application to complete the instruction. Otherwise, re-automatically assemble the service.

[0077] After receiving the microservice application completion instruction, the service quality is evaluated. If the quality meets the requirements, the microservice information that the archival workflow is about to execute is iteratively obtained until the archival workflow execution is completed; if the quality does not meet the requirements, the execution of the archival workflow is terminated, and the microservice information that does not meet the service quality is reported to the system administrator.

[0078] Example 2

[0079] Based on the above embodiments, Figure 2 As shown, the present invention also proposes a digital archive workflow modeling method, including:

[0080] Step 101: Obtain a digital archive operation request;

[0081] Step 102: Parse the operation request and extract user requirements;

[0082] Step 103: Based on the user needs extracted in step 102, a microservice set that can meet the user needs is selected from the microservice application set;

[0083] Step 104: Analyze the data dependencies of the microservice set selected in step 103 and calculate the optimal microservice provision order;

[0084] Step 105: Use the microservice set output in step 103 as nodes and the microservice provision order output in step 104 as directed edges to perform DAG modeling on the user request.

[0085] Example 3

[0086] Based on the above embodiments, Figure 3 As shown, the present invention also proposes a heterogeneous resource scheduling method based on mobile target defense, including:

[0087] Step 201: Obtain CVE vulnerability data online, and count the number of corresponding vulnerabilities based on the operating system types in the heterogeneous running resource pool;

[0088] Step 202: Use formula (1) to select the operating environment type corresponding to the initial microservice;

[0089] Step 203: Based on the output of step 202, select the corresponding image from the image library and instantiate it as the operating environment of the initial microservice;

[0090] Step 204: Use formula (2) to select the operating environment type corresponding to the non-initial microservice;

[0091] Step 205: Based on the output result of step 204, a corresponding image is selected from the image library and instantiated as the operating environment of the non-initial microservice.

[0092] Example 4

[0093] Based on the above embodiments, Figure 4 As shown, the present invention also proposes a microservice automatic assembly method for a heterogeneous operating environment, comprising:

[0094] Step 301: Complete the development of a microservice software module for digital archive management;

[0095] Step 302: Deploy the microservice software module in a container and store it in a mirrored mode;

[0096] Step 303: When a microservice automatic assembly command is received, the container file where the microservice is deployed is copied to the heterogeneous operating environment through an automated script;

[0097] Step 304: Complete the instantiation of the container through console commands in the running environment;

[0098] Step 305: The instantiated container automatically starts the microservice process;

[0099] Step 306: Determine whether the assembly of the microservice is completed by monitoring the fixed service port. If it is running normally, end the process; otherwise, re-execute step 303.

[0100] Example 5

[0101] Based on the above embodiments, Figure 5 As shown, the present invention also proposes a method for monitoring the operation of an archive workflow, comprising:

[0102] Step 401: Read the XML format file generated by the digital archive workflow generator to obtain the archive workflow model;

[0103] Step 402: Obtain the microservice information that the archive workflow is about to execute;

[0104] Step 403: Check the fixed service port to determine whether the microservice is running normally. If it is running normally, proceed to step 404; otherwise, proceed to step 405:

[0105] Step 404: Wait for the microservice to complete the instruction;

[0106] Step 405: Re-automatically assemble the service;

[0107] Step 406: After receiving the microservice completion instruction, the service quality is evaluated. If the quality meets the requirements, the process proceeds to step 408; if the quality does not meet the requirements, the process proceeds to step 407;

[0108] Step 407: Terminate the execution of the archive workflow and report the information of the microservice modules that do not meet the service quality to the system administrator;

[0109] Step 408: Iterate step 402 until the archive workflow is completed.

[0110] Example 6

[0111] Based on the above embodiments, Figure 6 As shown, the present invention also proposes a response method of a digital archive microservice system based on mobile target defense, comprising:

[0112] Step 501: Obtain a digital archive operation request;

[0113] Step 502: Activate the digital archive workflow generator to complete the archive workflow modeling;

[0114] Step 503: The digital archive workflow monitor loads the archive workflow model and selects the corresponding microservice according to the workflow running stage;

[0115] Step 504: Activate the mobile target defense scheduler and select the type of microservice operating environment to be executed;

[0116] Step 505: Activate the microservice assembler to complete the instantiation of the microservice;

[0117] Step 506: Send the dependency data to the corresponding microservice interface to complete the microservice response;

[0118] Step 507: Step 503 is iterated until the archive workflow is completed.

[0119] In summary, the present invention provides a digital archive microservice system based on mobile target defense. By implanting intrinsic security attributes such as dynamicity and heterogeneity into the digital archive information system based on the microservice architecture, it realizes the active defense capability against network attacks and improves the security of the digital archive information system.

[0120] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A digital archive microservice system based on mobile target defense, characterized in that: include: Digital archive workflow generator, microservice application collection, heterogeneous operation resource pool, mobile target defense scheduler, microservice assembler and digital archive workflow monitor; The digital archive workflow generator is used to automatically design a workflow model that meets user needs based on the application submitted by the user; The microservice application set is used to store the microservice application set corresponding to the entire digital archive management process in a mirrored form; The heterogeneous operation resource pool is used to store virtual machines corresponding to diverse operating systems in the form of images; The mobile target defense scheduler is used to schedule heterogeneous operating resources at different stages of the digital archive workflow with a certain probability to support service provision based on the mobile target defense concept; The microservice assembler is used to assemble the microservice application into the heterogeneous running resources selected by the mobile target defense scheduler according to the workflow model output by the digital archive workflow generator, thereby realizing the instantiation of the microservice function; The digital archive workflow monitor is used to track the entire process of the archive workflow and promptly discover and handle abnormal microservice applications.

2. A digital archive microservice system based on mobile target defense according to claim 1, characterized in that: The digital archive workflow generator is specifically used for: Obtain digital archive operation requests; parse the operation requests to extract user requirements; based on the extracted user requirements, select microservice applications that can meet the user requirements from the microservice application set; Analyze the data dependencies of the selected microservice applications and calculate the optimal microservice provision order; With the output microservice application as the node and the output microservice provision order as the directed edge, the user request is modeled as a directed acyclic graph to obtain a workflow model that meets the user's needs. The workflow model is stored in an XML format file.

3. A digital archive microservice system based on mobile target defense according to claim 1, characterized in that: Build the microservice application set as follows: Complete the development of microservice software modules for digital archive management; deploy the microservice software modules in containers and store them in mirror mode.

4. A digital archive microservice system based on mobile target defense according to claim 1, characterized in that: The mobile target defense scheduler is specifically used to: Obtain vulnerability data online through common vulnerability enumeration, and count the corresponding vulnerabilities based on the operating system types in the heterogeneous running resource pool; Convert the number of vulnerabilities in the operating system into a first scheduling probability, select the operating environment type corresponding to the initial microservice based on the first scheduling probability, select the corresponding system image from the image library and instantiate it as the operating environment of the initial microservice; The number of common vulnerabilities between the operating system to be scheduled and the operating environment type corresponding to the initial microservice is converted into a second scheduling probability. The operating environment type corresponding to the non-initial microservice is selected according to the second scheduling probability. The corresponding system image is selected from the image library and instantiated as the operating environment of the non-initial microservice.

5. A digital archive microservice system based on mobile target defense according to claim 4, characterized in that: The first scheduling probability is calculated as follows: where p i represents the first scheduling probability corresponding to the i-th type of operating system, o i represents the i-th type of operating system, v(o i ) represents the number of vulnerabilities of the i-th operating system.

6. A digital archive microservice system based on mobile target defense according to claim 4, characterized in that: The second scheduling probability is calculated as follows: where p′ i represents the second scheduling probability corresponding to the i-th type of operating system, o x The operating environment corresponding to the initial microservice of the archive workflow is the operating system, v(o x ,o i ) represents the operating system to be scheduled o i With o x The number of common mode vulnerabilities between 7. The digital archive microservice system based on mobile target defense according to claim 1 is characterized in that: The microservice assembler is specifically used to: When a microservice automatic assembly command is received, the container file where the microservice application is deployed is copied to the heterogeneous operating environment through an automated script; the container is instantiated through console commands in the operating environment; the instantiated container automatically starts the microservice process; and the fixed service port is monitored to determine whether the assembly of the microservice application is completed. If it is running normally, the process is terminated; otherwise, the process is re-executed.

8. The digital archive microservice system based on mobile target defense according to claim 1 is characterized in that: The digital archive workflow monitor is specifically used to: Read the XML format file generated by the digital archive workflow generator, obtain the archive workflow model, and obtain the microservice information that the archive workflow is about to execute; Check the fixed service port to determine whether the microservice application is running normally. If it is running normally, wait for the microservice application to complete the instruction. Otherwise, re-automatically assemble the service. After receiving the microservice application completion instruction, the service quality is evaluated. If the quality meets the requirements, the microservice information about the archive workflow to be executed is iteratively obtained until the archive workflow execution is completed; If the quality does not meet the requirements, the execution of the archive workflow will be terminated, and the microservice information that does not meet the service quality will be reported to the system administrator.

9. The digital archive microservice system based on mobile target defense according to claim 1 is characterized in that: The system's response process includes: Get digital archive operation request; Activate the digital archive workflow generator to complete the archive workflow modeling; The digital archive workflow monitor loads the archive workflow model and selects the corresponding microservice application from the microservice application set according to the workflow running stage; Activate the mobile target defense scheduler and select the operating environment type of the microservice application to be executed; Activate the microservice assembler to complete the instantiation of the microservice application; Send the dependent data to the corresponding microservice application interface to complete the microservice response; The iteration selects the corresponding microservice application from the microservice application set according to the workflow running stage until the archive workflow execution is completed.

Images