Application deployment updating method and system, electronic device and storage medium

Abstract

The application relates to the technical field of software updating, in particular to an application deployment updating method and system, an electronic device and a storage medium. The method comprises the following steps: acquiring a micro service; wherein the micro service comprises at least one micro service unit; the micro service unit comprises a list of deliverables and a dependency relationship between the micro service units; deploying the micro service and the deliverables to be deployed into a deliverable warehouse; acquiring the deliverables to be deployed from the deliverable warehouse according to the list of deliverables and the dependency relationship between the micro service units; and packaging the acquired deliverables according to requirements and then deploying the deliverables to a specified server. The application effectively standardizes and guides the whole software life cycle management. In the deployment stage, an operation and maintenance framework consumes the model data, so that the deployment and updating are more simple and efficient, and a multiplier effect is achieved.

Description

Technical Field

[0001] This invention relates to the field of software update technology, and in particular to application deployment update methods, systems, electronic devices, and storage media. Background Technology

[0002] Currently, microservice architecture is prevalent. While it brings architectural flexibility, it also presents challenges for product delivery, deployment, upgrades, and maintenance. From a technical architecture perspective, a microservice typically consists of multiple layers, such as: a foundation layer, a common component layer, a common service layer, and a business function layer, from bottom to top. Each layer has dependencies on each other, its own deliverables, and independent version releases. We call such layers microservice units. The finer the microservice unit breakdown, the higher the complexity of software development, testing, delivery, deployment, and upgrades. To address this technical issue, we propose an application deployment and update method, system, electronic devices, and storage media. Summary of the Invention

[0003] To address the technical problems existing in the prior art, this invention provides an application deployment and update method, system, electronic device, and storage medium. This invention establishes a unified microservice model that runs through the entire software lifecycle, including design, coding implementation, testing, and deliverable submission. During the deployment phase, the deployment tool performs deployment and upgrades based on this microservice model description.

[0004] To achieve the above objectives, the embodiments of the present invention provide the following technical solutions:

[0005] In a first aspect, in one embodiment of the present invention, an application deployment and update method is provided, the method comprising the following steps:

[0006] Obtain microservices;

[0007] The microservice includes at least one microservice unit; the microservice unit includes a list of deliverables and dependencies between microservice units.

[0008] Deploy the deliverables that need to be deployed and the acquired microservices into the deliverable repository;

[0009] Based on the list of deliverables included in the microservice unit and the dependencies between the microservice units, the deliverables that need to be deployed are retrieved from the deliverable repository, packaged according to requirements, and then deployed to the specified server.

[0010] As a further aspect of the present invention, after the deliverables are deployed to the designated server, the framework automatically updates the microservice list information, which includes file name, file size, file MD5 code, and file path information.

[0011] As a further aspect of the present invention, the microservice unit type includes business microservice units and non-business microservice units.

[0012] As a further embodiment of the present invention, the deliverable warehouse can be any type of test warehouse, UAT warehouse, or production warehouse.

[0013] As a further aspect of the present invention, the acquired deliverables are packaged according to requirements, and are packaged into any format such as ZIP, RPM, or Docker Image.

[0014] As a further aspect of the present invention, the method further includes updating the microservice, obtaining a list of deliverables before and after the update based on the updated microservice, comparing the obtained lists of deliverables before and after the update, and if there are any new deliverables, adding the new deliverables to the increment.

[0015] If there is an updated deliverable, compare the MD5 hash of the updated deliverable to obtain the increment that needs to be updated;

[0016] If there are any deleted deliverables, mark the deleted deliverables as deleted.

[0017] Package and deploy the incremental data.

[0018] Secondly, in another embodiment provided by the present invention, an application deployment and update system is provided, the system comprising:

[0019] Microservice acquisition module, deliverables, microservice migration module, and deployment module;

[0020] The microservice acquisition module is used to acquire microservices, wherein each microservice includes at least one microservice unit; the microservice unit includes a list of deliverables and the dependencies between microservice units.

[0021] The deliverables and microservices transfer module is used to deploy the deliverables and microservices to be deployed to the deliverables repository;

[0022] The deployment module is used to retrieve the deliverables to be deployed from the deliverable repository based on the list of deliverables included in the microservice unit and the dependencies between the microservice units, package the retrieved deliverables according to the requirements, and then deploy them to the specified server.

[0023] As a further aspect of the present invention, the system also includes an update module;

[0024] The update module is used to update the microservice. Based on the updated microservice, it obtains the deliverable list before and after the update and compares the obtained deliverable list before and after the update. If there is a new deliverable, it adds the new deliverable to the increment.

[0025] If there is an updated deliverable, compare the MD5 hash of the updated deliverable to obtain the increment that needs to be updated;

[0026] If there are any deleted deliverables, mark the deleted deliverables as deleted.

[0027] Package and deploy the incremental data.

[0028] Thirdly, in another embodiment of the present invention, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor loads and executes the computer program to implement the steps of the application deployment update method.

[0029] Fourthly, in another embodiment of the present invention, a storage medium is provided storing a computer program that, when loaded and executed by a processor, implements the steps of the application deployment update method.

[0030] The technical solution provided by this invention has the following beneficial effects:

[0031] This invention provides an application deployment and update method, system, electronic device, and storage medium. The method obtains microservices; wherein each microservice includes at least one microservice unit; each microservice unit includes a list of deliverables and dependencies between microservice units; the deliverables to be deployed and the obtained microservices are deployed to a deliverable repository; based on the list of deliverables included in the microservice unit and the dependencies between microservice units, the deliverables to be deployed are retrieved from the deliverable repository, the retrieved deliverables are packaged according to requirements, and then deployed to a designated server. This invention effectively standardizes and guides the entire software lifecycle management. During the deployment phase, the operations and maintenance framework consumes this model data, making deployment and updates simpler and more efficient, achieving twice the result with half the effort.

[0032] These or other aspects of the invention will become more apparent from the following description of embodiments. It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the invention.

[0033] These or other aspects of the invention will become more apparent from the following description of embodiments. It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the invention. BRIEF DESCRIPTION OF DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description only represent some of the embodiments of the present application, and other embodiments can be obtained by those skilled in the art without any creative effort on the basis of these drawings.

[0035] Figure 1 Flow chart of application deployment update method for an embodiment of the present application.

[0036] Figure 2 Structural block in application deployment update system for an embodiment of the present application Figure 1 .

[0037] Figure 3 Structural block in application deployment update system for an embodiment of the present application Figure 2 .

[0038] In the figure: microservice acquisition module-100, deliverable and microservice transfer module-200, deployment module-300, update module-400. DETAILED DESCRIPTION

[0039] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without any creative effort fall within the protection scope of the present application.

[0040] The flow chart shown in the drawings is only an example description, and does not necessarily include all the contents and operations / steps, nor does it have to be executed in the described order. For example, some operations / steps can be further decomposed, combined or partially merged, so the actual execution order can be changed according to the actual situation.

[0041] It should be understood that the terms used in the present application specification are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the present application specification and the appended claims, the singular forms "a", "an" and "the" are intended to include the plural forms unless the context clearly indicates otherwise.

[0042] Specifically, the embodiments of the present application will be further described below with reference to the drawings.

[0043] Please refer to Figure 1 , Figure 1A flowchart of an application deployment updating method provided by an embodiment of the present application is shown in FIG. 1. Figure 1 The application deployment updating method includes steps S10 to S40.

[0044] S10, acquiring a microservice, wherein the microservice includes at least one microservice unit; the microservice unit includes a list of deliverables and a dependency relationship between microservice units.

[0045] In an embodiment of the present application, the microservice unit is a part of the microservice, and clear boundaries are required between microservice units at each software life cycle stage, such as design, development, coding, packaging, testing, deployment, and maintenance upgrade.

[0046] In an embodiment of the present application, the microservice unit to be published externally must first define the microservice unit, and the descriptive file is published together with the installation package.

[0047] In an embodiment of the present application, the main attributes of the microservice unit further include: number, name, type, list of contained deliverables, and dependency relationship between microservice units.

[0048] The number must be unique and uniquely identified.

[0049] In an embodiment of the present application, the microservice unit type mainly includes: business microservice unit and non-business microservice unit. When selecting a microservice unit, the type plays a filtering role. Some microservice units may be pedestals, public components, public services, etc., and they have no business meaning. Other microservice units with business meaning depend on these infrastructures, and implementers only focus on microservice units with business meaning.

[0050] In an embodiment of the present application, the list of deliverables is the essence of microservice application deployment, which is the deployment of application deliverables. Each deliverable belongs to a microservice unit, which is a principle that must be followed by the microservice unit.

[0051] In an embodiment of the present application, the dependency relationship between microservice units, business microservice units depend on infrastructure, and public component or service microservice units also exist in general cases. Dependency is a chain structure, and only direct dependency is described. Indirect dependency is found through the dependency chain. Therefore, the top-level business microservice unit can obtain all microservice units through the dependency relationship.

[0052] S20, deploying the deliverables to be deployed and the acquired microservice to a deliverable warehouse;

[0053] In the embodiment of the application, a single microservice is composed of one or more microservice units, sometimes the application server of a user is insufficient, in order to reduce the number of application deployments, multiple business microservices are supported to be combined and deployed, but version checking is performed when the microservice is created, and it is checked whether there is a version conflict in infrastructure depended on by the multiple business microservices, and the business microservice units with the conflict need to be deployed separately.

[0054] The delivery warehouse is mainly used for storing deliveries, and an upgrade package of a product release is first updated to the delivery warehouse, and multiple microservice units can be set in each delivery warehouse.

[0055] S30, according to the list of deliveries included in the microservice unit and the dependency relationship between the microservice units, deliveries required to be deployed are obtained from the delivery warehouse, the obtained deliveries are packaged according to requirements, and then deployed to a specified server.

[0056] After the deployment is completed, the framework automatically updates microservice list information, and the list information includes file name, file size, file MD5 code, file path and the like.

[0057] Specifically, the obtained deliveries are packaged according to requirements, and can be packaged into formats such as ZIP, RPM and Docker Image.

[0058] In the embodiment of the application, the deliveries are deployed to the specified server by an operation and maintenance tool.

[0059] S40, the microservice is updated, the delivery list before and after the update is obtained based on the updated microservice, the obtained delivery list before and after the update is compared, if there is a new delivery, if the new delivery is added, the new delivery is added to the increment;

[0060] If there is an updated delivery, and the MD5 code of the compared updated delivery is obtained, the increment required to be updated is obtained.

[0061] If there is a deleted delivery, the deleted delivery is marked as a deleted state.

[0062] The increment is packaged and deployed.

[0063] The S40 further includes deleting the delivery marked as the deleted state.

[0064] The present application firstly updates the delivery object to the delivery object warehouse, then extracts the microservice corresponding delivery object based on the microservice model definition, and then repackages the delivery object into different file formats such as ZIP, RPM, Dock Image, etc., and finally deploys or upgrades.

[0065] The delivery object file information includes:

[0066] ID Unique Identifier String Name document String Path File path String MD5 File MD5 String Size File size Long

[0067] The microservice unit definition (MicroServiceUnit) is as shown in the following table:

[0068]

[0069] The file list supports specifying folders and files, some folders may be shared by multiple microservice units, and the files of other microservice units need to be excluded, and the ignored files can be set.

[0070] Specifically, the microservice unit definition includes: basic information definition, delivery object list definition and microservice unit dependency relationship definition.

[0071] a) Basic information definition

[0072] Role: product manager

[0073] Description: according to the responsibility of the microservice unit, determine the basic information of the microservice unit: number, name, type, number is unique and cannot be changed at will.

[0074] b) Delivery object list definition

[0075] Role: developer

[0076] Description: when adding a delivery object, update the delivery object list at the same time.

[0077] c) Microservice unit dependency relationship definition

[0078] Role: developer

[0079] Description: generally determine the dependency relationship when creating the microservice unit, and the dependency relationship can be adjusted in the middle.

[0080] The microservice definition (MicroService) is as shown in the following table:

[0081] ID Unique Identifier String CODE serial number String NAME name String DESCRIPTION describe String CreateTime Creation time Date

[0082] Specifically, the microservice definition includes:

[0083] Role: Implementer

[0084] Description: According to the product best practices and user needs, a business microservice unit and its dependent microservice units can be selected as a microservice for deployment, or multiple business microservice units can be selected for combined deployment to reduce the number of application service deployments.

[0085] Microservice-microservice unit association table

[0086] MicroServiceId Microservice ID String MicroServiceUnitCode Microservice unit number String

[0087] Microservices and microservices are in a many-to-many relationship.

[0088] The microservices that have been deployed are compared with the file MD5 code to obtain the increment. When there are many files, calculating the MD5 code is time-consuming. To improve the performance of obtaining the increment, the file MD5 code of the microservice is recorded for comparison during microservice deployment and upgrade.

[0089] Delivery warehouse information table:

[0090]

[0091]

[0092] According to the purpose of the delivery warehouse, it can be divided into test warehouse, UAT warehouse, and production warehouse. Different delivery warehouses are isolated from each other.

[0093] Specifically, the delivery warehouse definition includes:

[0094] Role: Implementer

[0095] Description: The main setting of the microservice unit list contained in the delivery warehouse.

[0096] The content upgrade of the delivery warehouse includes:

[0097] Role: Implementer, maintenance personnel

[0098] Description: When there is a new version of the microservice unit, the new version can be downloaded for update, and manual upload of the upgrade package for update is also supported.

[0099] Delivery warehouse-microservice unit association

[0100] ID Unique Identifier String RepositoryId Warehouse ID String Microservice Unit ID Microservice Unit ID String

[0101] The table describes the association between the warehouse and the microservice unit, and sets the warehouse to store the delivery of the microservice unit.

[0102] As can be seen from the above table, the microservice unit is the core model throughout the entire deployment update process.

[0103] Specifically, the microservice deployment and upgrade includes the following contents:

[0104] Microservice deployment

[0105] Role: implementation, operation and maintenance personnel

[0106] Description: The user selects the microservice to be deployed, and the system extracts the file from the delivery warehouse through the microservice description, the microservice unit description, the microservice unit and the delivery inclusion relationship, organizes the file in the directory, and then packs it into various forms of installation package through various packaging tools, such as ZIP, RPM, Docker, etc. File format.

[0107] Microservice incremental upgrade

[0108] Role: implementation, operation and maintenance personnel

[0109] Description: The user selects the microservice to be upgraded, and the system queries the current file version of the microservice and the file version in the delivery warehouse, compares them, obtains the increment, and then packs it into various file forms of increment package.

[0110] It should be understood that although the above is described in a certain order, these steps are not necessarily executed in the above order. Unless otherwise stated in this document, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, part of the steps of the present embodiment can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least part of other steps or steps or stages in other steps.

[0111] In an embodiment, referring to Figure 3 In the embodiment of the present application, an application deployment update system is also provided, which includes a microservice acquisition module 100, a delivery and microservice transfer module 200, and a deployment module 300.

[0112] The microservice acquisition module 100 is configured to acquire a microservice, wherein the microservice includes at least one microservice unit; and the microservice unit includes a list of deliveries and a dependency relationship between the microservice units.

[0113] In the embodiment of the present application, the microservice unit is a part of the microservice, and clear boundaries are required between the microservice units in each software life cycle stage, such as design, development, coding, packaging, testing, deployment, maintenance and upgrade.

[0114] In the embodiment of the present application, the microservice unit to be published externally must be defined first, and the descriptive file thereof is published together with the installation package.

[0115] In the embodiment of the present application, the main attributes of the microservice unit further include: number, name, type, list of deliverables, and dependency relationship between microservice units.

[0116] The number must be unique and uniquely identified.

[0117] In the embodiment of the present application, the types of the microservice unit mainly include: business microservice unit and non-business microservice unit. When the microservice unit is selected, the type plays a filtering role. Some microservice units may be bases, common components, common services and the like, and they have no business meaning. Other microservice units with business meaning depend on these infrastructures, and implementers only focus on the microservice units with business meaning.

[0118] In the embodiment of the present application, the list of deliverables is the deployment of the microservice application, and the essence is the deployment of the application deliverables. Each deliverable belongs to a microservice unit, which is a principle that must be followed by the microservice unit.

[0119] In the embodiment of the present application, the dependency relationship between the microservice units, the business microservice unit depends on the infrastructure, and the common component or service microservice unit also has dependency in general. The dependency is a chain structure, and only the direct dependency is described. The indirect dependency is found through the dependency chain. Therefore, the top-level business microservice unit can obtain all the microservice units through the dependency relationship.

[0120] The deliverable and microservice transfer module 200 is configured to deploy the deliverable and the microservice to the deliverable warehouse.

[0121] In the embodiment of the present application, a single microservice is composed of one or more microservice units. Sometimes, the application server of a user is insufficient, and in order to reduce the number of application deployments, multiple business microservices are selected for combined deployment. However, version checking is performed when the microservice is created, and whether there is a version conflict of the infrastructure depended on by the multiple business microservices is checked. The business microservice units with the conflict need to be deployed separately.

[0122] The delivery warehouse is mainly used for storing delivery, and the upgrade package of product release is first updated to the delivery warehouse, and multiple micro-service units can be set in each delivery warehouse.

[0123] The deployment module 300 is used for obtaining the delivery to be deployed from the delivery warehouse according to the list of the delivery included in the micro-service unit and the dependency relationship between the micro-service units, packaging the obtained delivery according to requirements, and then deploying to the specified server.

[0124] After the deployment is completed, the framework automatically updates the micro-service list information, and the list information includes file name, file size, file MD5 code, file path and the like.

[0125] Specifically, the obtained delivery can be packaged into ZIP, RPM, Docker Image and the like according to requirements.

[0126] In the embodiment of the application, the delivery is deployed to the specified server through the operation and maintenance tool.

[0127] In order to solve the problem of re-distribution of delivery, the delivery is first updated to the delivery warehouse, then the delivery corresponding to the micro-service is extracted based on the micro-service model definition, then the delivery is repackaged into different file formats such as ZIP, RPM, Dock Image and the like, and finally deployed or upgraded. The application takes the micro-service model as the core, effectively standardizes and guides the whole software life cycle management, and in the deployment stage, the operation and maintenance framework consumes the model data, so that the deployment and update are more simple and efficient, and the effect of achieving more with less is achieved.

[0128] Referring to Figure 3 In the embodiment of the application, an application deployment update system is also provided, and the system further includes an update module 400.

[0129] The update module 400 is used for updating the micro-service, obtaining the delivery list before and after the update based on the updated micro-service, comparing the obtained delivery list before and after the update; if there is a new delivery, if it is new, the new delivery is added to the increment;

[0130] If there is an updated delivery, and the MD5 code of the updated delivery is compared, the increment to be updated is obtained;

[0131] If there is a deleted delivery, the deleted delivery is marked as a deleted state;

[0132] The increment is packaged and deployed.

[0133] The updating module 400 is further configured to delete the delivery object marked as a deletion state.

[0134] In one embodiment, an electronic device is also provided in the embodiments of the present application, which comprises at least one processor, and a memory connected with the at least one processor, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the application deployment updating method, and the processor executes the instructions to implement the steps in the above method embodiments.

[0135] The electronic device comprises a user device and a network device. The user device includes, but is not limited to, a computer, a smart phone, a PDA, etc. The network device includes, but is not limited to, a single network server, a server group composed of multiple network servers, or a cloud composed of a large number of computers or network servers based on cloud computing. Cloud computing is a kind of distributed computing, which is a super virtual computer composed of a group of loosely coupled computer clusters. The electronic device can be operated independently to implement the present application, or can be connected to a network and interact with other electronic devices in the network to implement the present application. The network in which the electronic device is located includes, but is not limited to, the Internet, a wide area network, a metropolitan area network, a local area network, a VPN network, etc.

[0136] It should also be understood that the term "and / or" used in the specification and the appended claims of the present application means any combination of one or more of the associated listed items and all possible combinations, and includes these combinations.

[0137] In one embodiment of the present application, a storage medium is also provided, which stores a computer program, and the computer program is executed by a processor to implement the steps in the above method embodiments.

[0138] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be completed by a computer program instructing related hardware, and the computer program can be stored in a non-volatile computer readable storage medium, and when the computer program is executed, the processes of the above-mentioned embodiments can be included. Any reference to memory, storage, database or other medium used in the embodiments of the present application can include at least one of non-volatile and volatile memory.

[0139] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

[0140] The above are exemplary embodiments disclosed by the present application, but it should be noted that various changes and modifications can be made without departing from the scope of the embodiments disclosed by the present application as defined by the claims. The functions, steps and / or actions of the method claims described herein need not be performed in any particular order. Furthermore, although elements of the embodiments disclosed by the present application can be described or claimed in individual form, unless explicitly restricted, they can also be implemented in multiple forms.

[0141] It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "includes" and / or "including", as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. The embodiment number of the embodiments disclosed by the present application is only for description, and does not represent the advantages and disadvantages of the embodiments.

[0142] Those skilled in the art should understand that the above discussion of any of the embodiments is only exemplary, and is not intended to imply that the scope of the embodiments disclosed by the present application (including the claims) is limited to these examples; the technical features between the above embodiments or different embodiments can also be combined, and there are many other changes of the different aspects of the embodiments disclosed by the present application as described above. In order to be brief, they are not provided in detail. Therefore, any omissions, modifications, equivalent replacements, improvements, etc. made in the spirit and principles of the embodiments disclosed by the present application shall be included in the scope of protection of the embodiments disclosed by the present application.

Claims

1. An application deployment and update method, characterized in that, The method includes: Obtain microservices; The microservice includes at least one microservice unit; the microservice unit includes a list of deliverables and dependencies between microservice units; the microservice unit types include business microservice units and non-business microservice units. When selecting microservice units, the type serves as a filter, and implementers only focus on microservice units with business significance. A single microservice is composed of one or more microservice units. It supports the selection and deployment of multiple business microservices. When a microservice is created, a version check is performed to check whether there are version conflicts in the infrastructure that multiple business microservices depend on. If there are conflicts, the business microservice units are deployed separately. Deploy the deliverables that need to be deployed and the acquired microservices into the deliverable repository; Based on the list of deliverables included in the microservice unit and the dependencies between the microservice units, the deliverables that need to be deployed are retrieved from the deliverable repository, packaged according to requirements, and then deployed to the specified server. Once the deliverables are deployed to the designated server, the framework automatically updates the microservice list information, which includes filename, file size, file MD5 hash, and file path information. To update a microservice, obtain a list of deliverables before and after the update based on the updated microservice, and compare the obtained lists of deliverables before and after the update. If there are new deliverables, add them to the increment. If there are updated deliverables, compare their MD5 hashes to obtain the increment that needs to be updated. If there are deleted deliverables, mark them as deleted. Package and deploy the increment, and delete the deliverables marked as deleted.

2. The application deployment and update method as described in claim 1, characterized in that, The deliverable warehouse can be any type of testing warehouse, UAT warehouse, or production warehouse.

3. The application deployment and update method as described in claim 1, characterized in that, The acquired deliverables are packaged according to requirements, and are packaged into any format such as ZIP, RPM, or Docker Image.

4. An application deployment and update system, characterized in that, The system includes: a microservice acquisition module, a deliverables and microservice migration module, and a deployment module; The microservice acquisition module is used to acquire microservices, wherein each microservice includes at least one microservice unit; each microservice unit includes a list of deliverables and dependencies between microservice units; the microservice unit types include business microservice units and non-business microservice units. When selecting microservice units, the type serves as a filter, and implementers only focus on microservice units with business significance. A single microservice is composed of one or more microservice units. It supports the selection and deployment of multiple business microservices. When a microservice is created, a version check is performed to check whether there are version conflicts in the infrastructure that multiple business microservices depend on. If there are conflicts, the business microservice units are deployed separately. The deliverables and microservices transfer module is used to deploy the deliverables and microservices to be deployed to the deliverables repository; The deployment module is used to retrieve the deliverables to be deployed from the deliverable repository based on the list of deliverables included in the microservice unit and the dependencies between the microservice units, package the retrieved deliverables according to the requirements, and then deploy them to the specified server. Update module; The update module is used to update the microservice, obtain the deliverable list before and after the update based on the updated microservice, and compare the obtained deliverable list before and after the update; if there are new deliverables, the new deliverables are added to the increment. If there is an updated deliverable, compare the MD code of the updated deliverable to obtain the increment that needs to be updated; If there are any deleted deliverables, mark the deleted deliverables as deleted. Package and deploy the incremental deliverables, and delete the deliverables marked as deleted.

5. An electronic device comprising a memory and a processor, the memory storing a computer program, wherein the processor loads and executes the computer program to implement the steps of the application deployment update method as described in any one of claims 1-3.

6. A storage medium storing a computer program, which, when loaded and executed by a processor, implements the steps of the application deployment update method as described in any one of claims 1-3.

Images