CN117270953A

CN117270953A - Micro-service application management method and device and electronic equipment

Info

Publication number: CN117270953A
Application number: CN202311461187.0A
Authority: CN
Inventors: 易国强; 陈志列
Original assignee: Evoc Hi Tech Holdings Group Ltd
Current assignee: Evoc Hi Tech Holdings Group Ltd
Priority date: 2023-11-01
Filing date: 2023-11-01
Publication date: 2023-12-22

Abstract

The application is applicable to the technical field of micro services, and provides a micro service application management method, a micro service application management device and electronic equipment, wherein the method comprises the following steps: acquiring a micro-service application, and carrying out version management on the micro-service application by utilizing a pre-constructed micro-service management framework; the micro service management framework comprises a version authentication framework and a version management framework, wherein the version authentication framework is used for authenticating the micro service application, and the version management framework is used for carrying out version management on the micro service application according to an authentication result; the version management comprises version up management or version down management. The method and the device can improve the efficiency of micro-service application management.

Description

Micro-service application management method and device and electronic equipment

Technical Field

The application belongs to the technical field of micro services, and particularly relates to a micro service application management method, a micro service application management system, a micro service application management device, an electronic device and a computer readable storage medium.

Background

With the rapid development of software development, a micro-service architecture has become one of the main flows for building application programs. In the micro-service architecture, an application program is split into a plurality of micro-service applications, each micro-service application can be independently deployed and expanded, and the architecture can improve the scalability and maintainability of the application program and accelerate the development and deployment processes of the application program. In the prior art, when version management (such as new version online) is performed on a micro-service application, the management of the micro-service application is realized through various tools (such as approval tools, authentication tools, release tools and the like in the process, the method and the system based on the DevOps (Development, operations)), and the tools often need to be frequently switched for use due to different functions, and information among the tools is difficult to share, so that the efficiency of the management of the micro-service application is lower.

Disclosure of Invention

The embodiment of the application provides a micro-service application management method, a micro-service application management system, a micro-service application management device and electronic equipment, which can improve the efficiency of micro-service application management.

In a first aspect, an embodiment of the present application provides a method for managing a micro service application, including:

acquiring a micro-service application;

performing version management on the micro-service application by utilizing a pre-constructed micro-service management framework; the micro service management framework comprises a version authentication framework and a version management framework, wherein the version authentication framework is used for authenticating the micro service application, and the version management framework is used for carrying out version management on the micro service application according to an authentication result; the version management comprises version up management or version down management.

Optionally, before the version management of the micro service application by using the pre-built micro service management framework, the method further includes:

determining the version type of the micro-service application; the version type comprises a new version and an old version;

and in the case that the micro service application is a new version, performing version management on the micro service application by using a pre-constructed micro service management framework, including:

performing environment authentication on the micro-service application by utilizing the version authentication framework;

When the authentication result is that the environment authentication passes, the version management framework is utilized to carry out version release selection on the micro-service application;

and carrying out version management on the micro-service application according to the version release selection result.

Optionally, the performing the environment authentication on the micro service application by using the version authentication framework includes:

acquiring a configuration file of the micro service application, wherein the configuration file comprises environment parameters of the micro service application, and the environment parameters are used for controlling the version authentication framework to perform environment authentication on the micro service application;

and carrying out environment authentication on the micro-service application according to the environment parameters.

Optionally, the configuration file further includes release parameters, and the performing version release selection on the micro service application by using the version management framework includes:

and carrying out version release selection on the micro-service application according to release parameters in the configuration file and the version management framework.

Optionally, the performing version management on the micro service application according to the version release selection result includes:

and carrying out version management on the micro-service application according to a version release mode included in the version release selection result, wherein the version release mode comprises one of gray level release, direct release and version off-line.

Optionally, the method further comprises:

and generating the version number of the micro-service application according to the version release mode included in the version release selection result.

Optionally, in the case that the version release mode is gray release or direct release, the method further includes:

constructing a control file of the micro-service application, and performing version online management on the micro-service application by using the control file; the control file is constructed based on a preset release template, and the release template is a standard template constructed based on the online environment and/or online mode of different micro-service applications.

In a second aspect, an embodiment of the present application provides a micro service application management apparatus, including:

the application acquisition module is used for acquiring the micro-service application;

the micro-service application management module is used for carrying out version management on the micro-service application by utilizing a pre-constructed micro-service management framework; the micro service management framework comprises a version authentication framework and a version management framework, wherein the version authentication framework is used for authenticating the micro service application, and the version management framework is used for carrying out version management on the micro service application according to an authentication result; the version management comprises version up management or version down management.

In a third aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the steps of the micro service application management method described in the first aspect are implemented when the processor executes the computer program.

In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program, where the computer program implements the steps of the micro service application management method according to the first aspect, when the computer program is executed by a processor.

In a fifth aspect, embodiments of the present application provide a computer program product, which when run on an electronic device, causes the electronic device to perform the micro service application management method according to any one of the first aspects above.

Compared with the prior art, the embodiment of the application has the beneficial effects that:

the method and the device utilize the pre-constructed micro-service management framework to carry out version management on the micro-service application, and can improve the efficiency of managing the micro-service application. Specifically, the micro service management framework comprises a version authentication framework and a version management framework, the micro service application is authenticated through the version authentication framework, and is subjected to version management based on an authentication result through the version management framework. Meanwhile, the version authentication and version management of the micro-service application are in the same framework, so that the problem that information between tools is isolated and cannot be shared is solved, and the efficiency of the management of the micro-service application is further improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following description will briefly introduce the drawings that are needed in the embodiments or the description of the prior art, it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a method for managing micro-service applications according to an embodiment of the present application;

FIG. 2 is a flow chart of environment authentication according to user type according to an embodiment of the present application;

FIG. 3 is a flow diagram of version management of a micro service application provided by an embodiment of the present application;

fig. 4 is a schematic structural diagram of a micro service application management device according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, 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.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".

Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

While there are many types of DevOps tools available for use when using the micro-service architecture to build an application, these tools must be manually configured through a User Interface (User Interface) when in use, and when using different tools for micro-service deployment (e.g., at least one of testing, authentication, release, etc.), since the different tools have their own architecture and operation, the different tools need to be frequently switched, meaning that the automation management of the micro-service application is less, resulting in lower efficiency of micro-service application management. At the same time, the independence of different DevOps tools also makes information sharing and/or data exchange among the tools difficult, further resulting in low efficiency of micro-service application management.

In order to improve the efficiency of micro-service application management, the application provides a micro-service management framework comprising a version authentication framework and a version management framework.

Fig. 1 shows a flow chart of a micro service application management method according to an embodiment of the present application, which is described in detail below:

s1, acquiring the micro-service application.

In this embodiment of the present application, the micro service application refers to an application program to be subjected to version management or an independent service program split from a large-sized application program, for example, a new version APP that needs to be online or an old version APP that needs to be offline.

S2, carrying out version management on the micro-service application by utilizing a pre-constructed micro-service management framework; the micro service management framework comprises a version authentication framework and a version management framework, wherein the version authentication framework is used for authenticating the micro service application, and the version management framework is used for carrying out version management on the micro service application according to an authentication result; the version management includes version up management or version down management.

In the embodiment of the present application, the version authentication framework and the version management framework are integrated in the foregoing micro service management framework, so that the micro service application can be authenticated in one framework, and the version of the micro service application can be managed according to the authentication result. The version management means that a corresponding version release mode is selected for the micro-service application, and the micro-service application is online according to the selected version release mode, for example, the micro-service application is online by using a gray release mode; the version offline management is used for offline the selected micro-service application, for example, when the new version of the micro-service application meets the online requirement, the old version of the micro-service application is offline, or when the new version of the micro-service application does not meet the online requirement, the new version of the micro-service application is offline.

In another optional embodiment of the present application, before the performing version management on the micro service application by using the pre-built micro service management framework, the method further includes:

constructing a version authentication framework by using a preset authentication tool and constructing a version management framework by using a preset release tool; the authentication tool is used for carrying out environment authentication on the micro-service application to obtain an authentication result; the release tool is used for carrying out version management on the micro-service application based on the version release mode of the micro-service application.

In some embodiments, the authentication tool may include a code and document management tool (for example, gitLab) and a source code detection tool (for example, sonarQube) and the like, and is configured to detect an environment to be issued of the micro service application and obtain an authentication result, for example, detect the environment to be issued of the micro service application a, and if the authentication result is that the test environment passes the authentication, it is indicated that the micro service application a will issue to the test environment. The release tool may include a persistent delivery tool (such as an Argo CD), a persistent integration tool (such as Jenkins), etc. for automatic delivery according to the version release of the micro-service application. The application can integrate a plurality of tools (such as GitLab, sonarQube, argo CD, jenkins and Istio and the like) based on the Groovy engine, so that the plurality of tools are opened under one framework, and data sharing of the plurality of tools is realized.

In other embodiments, the authentication may also include user type authentication (detecting identity rights of different users) or code authentication (detecting release rights of a specific code), and so on. For example, when the micro-service application is pipelined (i.e. micro-service management), a group tag to which the current login user belongs is acquired, enumeration is performed through the group tag to determine whether the current login user has the authority of the current execution environment, if false, an error log is output and the pipelining is finished, and if true, execution is continued.

determining the version type of the micro-service application; the version types include new versions and old versions.

Correspondingly, when the micro service application is a new version, the method for managing the version of the micro service application by using the pre-built micro service management framework includes:

performing environment authentication on the micro-service application by using the version authentication framework;

It should be noted that, because the micro service management framework in the application integrates the version authentication framework and the version management framework at the same time, for the micro service application of the new version, the processing such as testing and authentication needs to be performed, so that the version authentication framework is used for authentication, and then the version management framework is used for version management; for the old version micro-service application which does not need testing and authentication, the version management framework is directly utilized for version management.

In some embodiments, the authentication result includes that the environment authentication is passed and the environment authentication is not passed, and under the condition that the environment authentication is not passed, the environment to be issued of the current micro service application is not identified, an error log is output, and the pipeline operation is finished; in the case that the environment authentication is passed, the environment to be issued of the current micro service application is identified, for example, the environment to be issued of the current micro service application is identified as a test environment. The version management framework performs version release selection on the micro-service application in an environment with environment authentication passing, performs version management on the micro-service application according to a version release selection result, does not need to manually switch other tools to release after authentication, can complete management of all the micro-service application in the same framework, and can improve flexibility, scalability and maintainability of management of the micro-service application.

In this embodiment of the present application, the performing, by using the version authentication framework, environment authentication on the micro service application includes:

In some embodiments, the configuration file includes configuration parameters, such as environment parameters, of the micro service application for program setting, for determining an environment to be deployed of the micro service application. The environment authentication may include at least one of test environment authentication, development environment authentication, and production environment authentication, and the corresponding environment authentication is issued to the environment indicated by the environment parameter when passing. For example, the environment parameter may be an "env_type" field to indicate the environment to be deployed of the micro-service application. The present application may manage the authentication of the micro service application by the version control function of the GitLab by storing the configuration file of the micro service application in the GitLab.

In other embodiments, the environment to be published may also be determined through user type authentication, i.e. the environment authentication is performed according to the detected user type, for example, referring to fig. 2, if the user submitting the micro-service application is detected as a tester, the user submitting the micro-service application is correspondingly published to the test environment; when detecting that the user submitting the micro-service application is a developer, correspondingly publishing the micro-service application to a development environment; and when detecting that the user submitting the micro-service application is an operation and maintenance person, correspondingly issuing the micro-service application to a development environment after issuing approval.

In an optional embodiment of the present application, the user may be classified into types and rights, and specifically, the types of user classification include: system administrators, specific authorized users, and general users. Wherein, system administrator authority: all release items can be checked, the release items can be released to all environments including production environments, and a secondary auditing process is not needed when the release items are released to the production environments, wherein the secondary auditing process is used for ensuring that the finally released environments are audited by the production environments; specific authorized user rights: all release items can be checked, and the release items can be released to all environments including the production environment, and a secondary auditing process is not required when the release items are released to the production environment; ordinary user rights: after authorization, the user can see the release item corresponding to the authorization, and can release the corresponding environment by adding a specific group, and when releasing to the production environment, approval is required, for example, when a user with ordinary user authority joins in a test group, the user can only release to the test environment, and when releasing to the production environment, approval is required.

In this embodiment of the present application, the configuration file further includes release parameters, and the performing version release selection on the micro service application by using the version management framework includes:

And carrying out version release selection on the micro service application according to release parameters in the configuration file.

In some embodiments, the release parameter is a configuration parameter for indicating a version release mode, and the release parameter is used to select a corresponding version release mode, so that a user can accurately select a required version release mode. For example, the Release parameter may be a "gray_release" field, which indicates whether to Release Gray, and if the "gray_release" field is set to True, the manner in which Gray Release is selected is indicated.

In this embodiment of the present application, the performing version management on the micro service application according to the version release selection result includes:

The gray release (canary release) refers to a release mode capable of enabling a new version and an old version of micro-service application to carry out smooth transition, namely enabling a part of users to continue to use the old version of micro-service application, enabling a part of users to start to use the new version of micro-service application, if the new version of micro-service application can meet the user requirements, gradually expanding the user range, transferring all users to the new version of micro-service application, ensuring that the new version and the old version of micro-service application are simultaneously online after the gray release is successful, and carrying out flow distribution by adopting a default flow proportion mode; direct publishing refers to directly sending the micro-service application to the corresponding environment to be published; the release offline is to take the micro-service application of a specific version out of the production environment, and the specific version can be the micro-service application of a new version or the micro-service application of an old version.

In some embodiments, the version release mode includes one of gray level release, direct release and version offline, and since release environments of the micro service application are different, it is necessary to adapt to different version release modes to perform version online. For version management of micro-service applications in a test environment and a development environment, since the repaired bug is updated and a new function is added, the version management is released in a direct release mode; for version management of micro-service applications in a production environment, since the update iteration of the micro-service application actually used by a user is involved, a gray release mode is adopted, that is, a preset flow proportion mode is used for distributing flow, for example, for an old version of micro-service application A and a new version of micro-service application B, a part of users continue to use the micro-service application A, a part of users start to use the micro-service application B, if the users have no objection to the micro-service application B, the flow range is gradually expanded, and all users are gradually migrated to the micro-service application B. The stability of integral release can be ensured through gray release, problems can be found and adjusted in the initial gray release process, and the maintenance is convenient. Version offline is to offline a particular version of the micro-service application, and this function can select an offline gray-scale version (i.e., a new version of the micro-service application) or a regular version (i.e., an old version of the micro-service application), either of which the other version is to take over all traffic.

In another optional embodiment of the present application, further comprising: and generating the version number of the micro-service application according to the version release mode included in the version release selection result.

In some embodiments, the version numbers described above are used to identify unique microservice applications, for example using the "Primary. Secondary. Add" three-level version number definition commonly used in the industry. Since the direct release is not released to the actual production environment, the source code BRANCH (branch_name) and the environment (env_type) to be released can be selected without filling in the version number. And because the new and old versions provide services on line at the same time when the gray level is released, the flow distribution is carried out through different weights or labels, the version number is required to be set when the gray level is released, and therefore flow control and release history tracing are carried out on different versions of micro-service applications.

In an alternative embodiment, the present application may generate the version number in three ways:

1. setting version numbers by page parameters

Setting a Version number according to a Version field of a page for executing Version management, wherein a character string is intercepted into a pure number to avoid sensitive words;

2. setting version number by version number of currently online microservice application

Defaulting to take the version number of the current online micro-service application as the version number of the newly released micro-service application, wherein the scene is not suitable for gray release and can be used when the version number is required to be filled in a test environment or a development environment;

3. task id managed by current version as version number

The version number is not set when version management is performed and this micro-service application has never been published, at which point the task id of the current stream version management is defaulted as the version number.

In another optional embodiment of the present application, in a case where the version release manner is gray release or direct release, the method further includes:

In some embodiments, for the case that the version release mode is gray release or direct release, the configuration parameters such as the environment parameters and release parameters corresponding to the micro-service application are filled into a preset release template to obtain a control file of the micro-service application, and the control file is used for realizing automatic online of the micro-service application. Also, for version offline, automatic offline of the micro-service application is also achieved in a similar manner by template population. For example, using the Global Pipeline Libraries method in the jenkins shared template library, template rendering (i.e., filling configuration parameters into a preset release template to obtain a control file for the micro-service application) and version release are implemented, and the release template is rendered by defining the release template in jenkins and then calling the method in Global Pipeline Libraries to obtain the control file.

In another optional embodiment of the present application, after performing version management on the micro service application by using the pre-built micro service management framework, the method further includes:

pushing the version management result to a preset communication tool.

In some embodiments, the version management result includes successful online of the micro service application or successful offline of the micro service application. The preset communication tool can be a third party communication tool supporting a Webhook pushing mode. By pushing the version management result to the preset communication tool, the trace of the micro service application can be facilitated, and the maintainability of the micro service application management is improved. Referring to fig. 3, which is a version management flowchart of a micro-service application, in fig. 3, after login authentication, authentication is performed once, that is, authentication of a release environment, after authentication of the release environment is passed (that is, an environment to be released is determined), a corresponding version release mode is determined, and for gray release or direct release, in order to improve accuracy of release of the micro-service application, secondary audit is performed again after compiling (i.e., compiling configuration parameters and the like) and rendering a template, so that message pushing is ensured after release to a production environment; for the version offline, if the offline is successful, the message is pushed directly, and if the offline is failed, the version management is performed again. After stencil rendering, either version up (i.e., CD deployment) or version down (i.e., CD cropping) is automatically achieved by the Argo CD tool. Meanwhile, the whole micro-service management framework has realized multi-tool integration, and all version management data (such as configuration files, control files and the like) are uniformly managed, so that when the version fails to be online, the version rollback function can be realized by redeploying the history version micro-service application.

It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.

Corresponding to the micro service application management method described in the above embodiments, fig. 4 shows a schematic structural diagram of the micro service application management device provided in the embodiment of the present application, and for convenience of explanation, only the portions related to the embodiments of the present application are shown.

Referring to fig. 4, the apparatus may be a micro service application management apparatus 41, and the micro service application management apparatus 41 may include an application acquisition module 411 and a micro service application management module 412.

Referring to fig. 4, the micro service application management apparatus 41 includes:

the application acquisition module 411 is configured to acquire a micro-service application;

the micro service application management module 412 is configured to perform version management on the micro service application by using a pre-constructed micro service management framework; the micro service management framework comprises a version authentication framework and a version management framework, wherein the version authentication framework is used for authenticating the micro service application, and the version management framework is used for carrying out version management on the micro service application according to an authentication result; the version management comprises version up management or version down management.

In some embodiments, the micro service application management apparatus 41 further includes a framework construction module, where before the framework construction module is configured to perform version management on the micro service application by using the pre-constructed micro service management framework, the framework construction module includes:

constructing a version authentication framework by using a preset authentication tool and constructing a version management framework by using a preset release tool; the authentication tool is used for carrying out environment authentication on the micro-service application to obtain an authentication result; the release tool is used for carrying out version management on the micro-service application based on a version release mode of the micro-service application.

In some embodiments, the micro service application management apparatus 41 further includes a type determining module, where before the type determining module is configured to perform version management on the micro service application by using the pre-built micro service management framework, the type determining module includes:

determining the version type of the micro-service application; the version types include a new version and an old version.

Correspondingly, in the case that the micro service application is a new version, the micro service application management module 412 performs version management on the micro service application using a pre-built micro service management framework by the following operations, including:

In some embodiments, the micro service application management module 412 performs the environment authentication on the micro service application by using the version authentication framework through the following steps, including:

In some embodiments, the micro service application management module 412 uses the version management framework to make version release selections for the micro service application by:

In some embodiments, the micro service application management module 412 performs version management on the micro service application according to the version release selection result by the following steps, including:

In another alternative embodiment, the micro service application management device 41 further includes a version number building module, where the version number building module is configured to generate a version number of the micro service application according to a version publishing manner included in the version publishing selection result.

In another optional embodiment, the micro service application management device 41 further includes a template generating module, where the template generating module is configured to, when the version release manner is gray release or direct release, include:

In another alternative embodiment, the micro service application management apparatus 41 further includes a message pushing module, where the message pushing module is configured to, after the performing version management on the micro service application by using the pre-built micro service management framework, include:

Pushing the version management result to a preset communication tool.

It should be noted that, because the content of information interaction and execution process between the devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and details thereof are not repeated herein.

Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 5, the electronic apparatus 5 of this embodiment includes: at least one processor 50 (only one shown in fig. 5), a memory 51, and a computer program 52 stored in the memory 51 and executable on the at least one processor 50. The steps of any of the various method embodiments are performed by the processor 50 when executing the computer program 52.

The electronic device 5 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, etc. The electronic device may include, but is not limited to, a processor 50, a memory 51. It will be appreciated by those skilled in the art that fig. 5 is merely an example of the electronic device 5 and is not meant to be limiting as the electronic device 5 may include more or fewer components than shown, or may combine certain components, or different components, e.g., the electronic device may further include an input transmitting device, a network access device, a bus, etc.

The processor 50 may be a central processing unit (Central Processing Unit, CPU), other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 51 may in some embodiments be an internal storage unit of the electronic device 5, such as a hard disk or a memory of the electronic device 5. The memory 51 may be an external storage device of the electronic device 5, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the electronic device 5. Further, the memory 51 may also include both an internal storage unit and an external storage device of the electronic device 5. The memory 51 is used for storing an operating system, application programs, boot loader (BootLoader), data, other programs, etc., such as program codes of the computer program. The memory 51 may also be used to temporarily store data that has been transmitted or is to be transmitted.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the division of the functional units and modules is illustrated, and in practical application, the functional distribution may be performed by different functional units and modules, that is, the internal structure of the apparatus is divided into different functional units or modules, so as to perform all or part of the functions described above. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.

The embodiment of the application also provides a network device, which comprises: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, the processor implementing the steps in any of the various method embodiments when the computer program is executed.

Embodiments of the present application also provide a computer readable storage medium storing a computer program which, when executed by a processor, implements steps in the various method embodiments.

Embodiments of the present application provide a computer program product which, when run on an electronic device, causes the electronic device to perform steps that may be implemented in the various method embodiments described.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. With such understanding, the present application implements all or part of the flow of the method of the embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of the method embodiments. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a camera device/electronic apparatus, a recording medium, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

In the embodiments, the descriptions of the embodiments are focused on, and the parts of a certain embodiment that are not described or depicted in detail can be referred to for related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other manners. For example, the apparatus/network device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims

1. A method of micro-service application management, comprising:

acquiring a micro-service application;

2. The method for managing micro-service applications according to claim 1, wherein before the version management of the micro-service applications by using the pre-built micro-service management framework, further comprising:

3. The micro service application management method as claimed in claim 2, wherein said performing the environment authentication on the micro service application using the version authentication framework comprises:

4. The method for managing micro service applications according to claim 3, wherein the configuration file further comprises release parameters, and the selecting the release of the version of the micro service application by using the version management framework comprises:

5. The method for managing micro-service applications according to claim 2, wherein said performing version management on said micro-service applications according to a version release selection result comprises:

6. The micro service application management method as claimed in claim 5, further comprising:

7. The micro service application management method according to claim 5, wherein in the case where the version release mode is gray release or direct release, further comprising:

8. A micro service application management apparatus, comprising:

9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 7 when the computer program is executed.

10. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the method according to any one of claims 1 to 7.