CN114968286A - Microservice publishing method, device, storage medium and electronic device - Google Patents

Abstract

The application discloses a micro-service publishing method, a micro-service publishing device, a storage medium and electronic equipment. Wherein, the method comprises the following steps: configuring service basic information and deployment information, wherein the service basic information at least comprises a service name of a service to be published; receiving a service release request of a target object, wherein the service release request at least carries identification information corresponding to a plurality of target services to be released and the dependency relationship of the plurality of target services; determining the issuing priority of each target service in the plurality of target services according to the dependency relationship of the plurality of target services; and releasing each target service in batch according to the release priority, the service basic information and the deployment information. The method and the system solve the technical problems that due to the fact that the business system completes micro-service transformation, the service quantity is greatly increased, new services are published and upgraded through Jenkins, development, operation and maintenance communication cost is high, publication time is long, and the technical problems such as actual requirements cannot be met.

Description

Microservice publishing method, device, storage medium and electronic device

technical field

The present application relates to the field of cloud native, in particular, to a microservice publishing method, apparatus, storage medium and electronic device.

Background technique

In order to make the service more stable and flexible, the application system can be transformed with micro-services. After the transformation, the number of services can be increased from the previous hundreds to thousands. At the same time, the business system may need to be upgraded regularly. The number of services upgraded each time Up to hundreds.

In related technologies, new services can generally be released and upgraded through Jenkins, but this method has technical problems such as high development and operation and maintenance communication costs, long release time, and inability to meet actual needs.

For the above problems, no effective solution has been proposed yet.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a microservice publishing method, device, storage medium, and electronic device, so as to at least solve the problem that due to the completion of the microservice transformation of the business system, the number of services has greatly increased, and new services are published and upgraded through Jenkins. Technical problems such as high development and operation and maintenance communication costs, long release time, and inability to meet actual needs.

According to an aspect of the embodiments of the present application, a method for publishing microservices is provided. The method is applied in a cloud native environment and includes: configuring basic service information and deployment information, wherein the basic service information includes at least the service name of the service to be published. , the deployment information includes at least the running location of the service to be published and the number of instances to be started; receiving a service publishing request from the target object, wherein the service publishing request at least carries the identification information corresponding to the multiple target services to be published, and the multiple target services. Service dependencies; determine the release priority of each target service in the multiple target services according to the dependencies of the multiple target services; batch release each target service according to the release priority, basic service information and deployment information.

Optionally, according to the release priority, service basic information and deployment information, each target service is released in batches, including: detecting whether the target time is the scheduled upgrade time, and in the case of the target time being the scheduled upgrade time, reading the list of services to be published, The list of services to be released includes: each target service; query the basic information of the target service and target deployment information corresponding to each target service; determine the release order of each target service according to the release priority, and according to the release order, the basic information of the target service and the target deployment Information release target service.

Optionally, determining the release order of each target service according to the release priority, and publishing the target service according to the release order, the basic information of the target service and the target deployment information, including: detecting the first target service currently to be released among the plurality of target services, and judging. Whether there is a dependent service in the first target service, obtain a judgment result; if the judgment result indicates that the first target service does not have a dependent service, publish the first target service basic information and the first target deployment information corresponding to the first target service. A target service.

Optionally, determining the release order of each target service according to the release priority, and publishing the target service according to the release order, the basic information of the target service and the target deployment information, including: detecting the first target service currently to be released among the plurality of target services, and judging. Whether there is a dependent service in the first target service, a judgment result is obtained; if the judgment result indicates that the first target service has a dependent service, the dependent service is published, wherein the dependency of the dependent service includes: a common dependency relationship and a strong dependency relationship. Dependencies take precedence over normal dependencies.

Optionally, publishing the dependent service includes: detecting whether the dependent service is successfully published, and when the dependent service fails to publish, stopping publishing the first target service.

Optionally, in the case that the dependent service is successfully published, the first target service is published.

Optionally, in the event that the first target service fails to be published, the dependent service is rolled back to the state before the publication

According to another aspect of the embodiments of the present application, a microservice publishing apparatus is further provided, which is characterized by comprising: a configuration module configured to configure basic service information and deployment information, wherein the basic service information includes at least an indication of a service to be published The deployment information includes at least the running location of the service to be published and the number of instances to be started; the receiving module is used to receive the service publishing request of the target object, wherein the service publishing request at least carries a plurality of target services to be published corresponding to each identification information, and the dependencies of multiple target services; the determination module is used to determine the release priority of each target service in the multiple target services according to the dependencies of the multiple target services; the release module is used to determine the release priority of each target service according to the release priority , service basic information and deployment information to publish each target service in batches.

According to another aspect of the embodiments of the present application, a non-volatile storage medium is also provided, wherein the storage medium includes a stored program, and when the program is running, the device where the storage medium is located is controlled to execute any microservice publish method.

According to another aspect of the embodiments of the present application, an electronic device is further provided, which is characterized by comprising: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to achieve Any microservice publishing method.

In the embodiment of the present application, in the cloud native environment, the intelligent publishing system based on metadata configuration publishes micro-services, by configuring basic service information and deployment information, receiving service publishing requests from target objects and according to multiple target services. The dependency relationship determines the release priority of each target service in multiple target services, and achieves the purpose of intelligently releasing the service to be upgraded to its corresponding operating platform according to the release priority, simplifying the operation and maintenance work and improving the deployment efficiency. The complex logic of the sequence is presented in front of the development and operation and maintenance personnel in the form of simple expressions, and the technical effect of the execution is automatically and intelligently analyzed by the system, which solves the problem that the number of services has increased significantly due to the completion of the microservice transformation of the business system. Through Jenkins The release and upgrade of new services cause technical problems such as high development and operation and maintenance communication costs, long release time, and technical problems that cannot meet actual needs.

Description of drawings

The drawings described herein are used to provide further understanding of the present application and constitute a part of the present application. The schematic embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation of the present application. In the attached image:

1 is a flowchart of an optional method for publishing a service according to an embodiment of the present application;

FIG. 2 is a flowchart of implementation steps of an optional cloud-native intelligent publishing system according to an embodiment of the present application;

3 is a schematic diagram of an optional intelligent publishing module division according to an embodiment of the present application;

4 is a schematic structural diagram of an optional microservice publishing apparatus according to an embodiment of the present application;

FIG. 5 is a schematic block diagram of an optional exemplary electronic device according to an embodiment of the present application.

Detailed ways

In order to make those skilled in the art better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only The embodiments are part of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the scope of protection of the present application.

It should be noted that the terms "first", "second", etc. in the description and claims of the present application and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It is to be understood that data so used may be interchanged under appropriate circumstances so that the embodiments of the application described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

In order to facilitate those skilled in the art to better understand the relevant embodiments of the present application, the technical terms or some terms that may be involved in the embodiments of the present application are now explained as follows:

SLA is the abbreviation of Service-Level Agreement. The Chinese name is: Service-Level Agreement. It is generally a promise made by both parties to the agreement. In the field of operation and maintenance, a very important result indicator is the SLA of the system. a promise. There are generally two ways to customize the system SLA, one is to measure and calculate through the time dimension, and the other is to measure and calculate through the user request status.

Pod is a concept proposed by Kubernetes for deploying, managing, and orchestrating containerized applications. It is also the smallest deployment unit in Kubernetes. Literally translated, it means "pod"; it is a container group composed of a group of tightly coupled containers. Will be consistently scheduled, deployed on the same node, and run in a "shared environment". The "shared environment" here includes: all containers share an IP address and port space; allow containers to share storage volumes and exchange information through the file system; containers can communicate through IPC (inter-process communication).

According to an embodiment of the present application, an embodiment of a method for publishing microservices is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings may be executed in a computer system such as a set of computer-executable instructions, and, Although a logical order is shown in the flowcharts, in some cases steps shown or described may be performed in an order different from that herein.

FIG. 1 is a method for publishing microservices according to an embodiment of the present application. As shown in FIG. 1 , the method includes the following steps:

Step S102, configure basic service information and deployment information, wherein the basic service information includes at least the service name of the service to be published, and the deployment information at least includes the running location of the service to be published and the number of instances to be started.

In step S102, the basic service information and deployment information are metadataized first, and then the basic service information and deployment information are configured, thereby connecting the intelligent publishing platform to the authentication of the container cloud cluster, so that the server can be called for Service management.

Step S104: Receive a service release request from the target object, wherein the service release request at least carries identification information corresponding to multiple target services to be released, and dependencies of the multiple target services.

In step S104, the service release request of the target object is accepted, which can be completed by the developer. The target service carried in the service release request has different types, and each type has its own corresponding identification information, and the target service can be determined according to the identification information. The kind of service and the dependencies of each target service.

For example, services can be divided into services with dependencies and services without dependencies. A service without dependencies is called this service, and its identification information is recorded as dep. Services with dependencies can be divided into ordinary dependencies. Services and services with strong dependencies, where common dependencies are recorded as dep+, and strong dependencies are recorded as dep++.

Step S106, determining the release priority of each target service in the plurality of target services according to the dependencies of the plurality of target services.

In step S106, the dependencies of the multiple target services at least include: common dependencies and strong dependencies, wherein the priority of the strong dependencies is stronger than that of the normal dependencies.

For example, for example, the release of service A strongly depends on the release of service B first and the database script C is executed, and the configuration is Adep B+, A dep C+, and the execution priority of automatic configuration B and C is higher than that of A.

Step S108: Publish each target service in batches according to the publishing priority, basic service information and deployment information.

In step S108, when publishing in batches, according to the priority order of publishing, the services with higher priorities are published first, and then the services with lower priorities are published.

It should be noted that, before publishing the target service, it is first detected whether the target time is the scheduled upgrade time, and then if the target time is determined to be the scheduled upgrade time, the list of services to be published is read, wherein the list of services to be published includes: each target service; query the basic information of the target service and target deployment information corresponding to each target service; determine the release order of each target service according to the release priority, and release the target service according to the release order, the basic information of the target service and the target deployment information.

Optionally, publishing the target service based on the target service basic information and target deployment information according to the publishing sequence includes: detecting a first target service currently to be published among multiple target services, judging whether the first target service has a dependent service, and obtaining a judgment result .

In some optional embodiments of the present application, specifically, if the judgment result indicates that the first target service does not have a dependent service, the first target service is published according to the basic information of the first target service corresponding to the first target service and the first target deployment information. For the service, if the judgment result indicates that the first target service has a dependent service, the dependent service is published, wherein the dependencies of the dependent service include: common dependencies and strong dependencies, and the priority of strong dependencies is higher than that of common dependencies.

It should be noted that after publishing the dependent service, it is necessary to check whether the dependent service is successfully published. If the dependent service fails to be published, stop publishing the first target service; if the dependent service is successfully published, publish the first target service; In the case of service release failure, the dependent service is rolled back to the state before release.

For example, when publishing in batches, first publish services with high priority and check their dependencies. If a strongly dependent service is not published, push the service into the stack and publish the strongly dependent service first. If the strongly dependent service fails to publish , then the service will stop publishing: For example, in the above example, when A publishes, check whether B and C are published successfully, if B is not published, then publish B service first, if B fails to publish, A will also stop publishing; if A fails to publish , the B and C services that are strongly associated and successfully released will be rolled back if they are in the dep++ strong dependency mode.

FIG. 2 is a flowchart of the implementation steps of an optional cloud-native intelligent publishing system according to an embodiment of the present application. As shown in FIG. 2 , first configure basic service information and deployment information, and then determine whether to apply for publishing There is a dependency relationship. If there is no dependency relationship, the service will be published directly. If there is a dependency relationship, the service is currently in a dependent service state, and then it is judged whether the dependent service has been published. If not, the dependent service will be published directly.

FIG. 3 is a schematic diagram of an optional intelligent publishing module division according to an embodiment of the present application. As shown in Figure 3, the module includes:

The microservice management module is used to maintain the basic information and deployment information of microservices. The basic service information includes service name, business, SLA indicators, etc., and deployment information includes the cluster to which it belongs, namespace, number of PODs, health check scripts, and releases. success signs etc.

The intelligent publishing module defines dependency expressions, provides graphical display functions and a parsing engine, and ensures that services are published in the correct order;

The cloud native platform module, the container orchestration platform, provides an operating environment for services, manages the full life cycle of services, and provides external API interfaces.

In this intelligent publishing module division, the microservice management module is used to maintain the basic information and deployment information of microservices. The basic service information includes service name, business, SLA indicators, etc. Number of PODs, health check scripts, release success signs, etc. The intelligent publishing module defines dependency expressions, provides a graphical display function and an analysis engine, and ensures that services are published in the correct order; the cloud native platform module, the container orchestration platform, provides a running environment for services, manages the full life cycle of services, and provides external Provides an API interface to intelligently release the services to be upgraded to their respective operating platforms according to the release priority, simplifying the operation and maintenance work and improving the deployment efficiency, thereby realizing the complex logic of the release sequence in the form of simple expressions. , in front of the operation and maintenance personnel, and through the system's automatic and intelligent analysis of the technical effect of execution, it solves the problem of how to use the network call relationship between these services due to the completion of the micro-service transformation of the business system and the large increase in the number of services. The complex logic of the release order presents technical issues in a simple way.

FIG. 4 is a microservice publishing apparatus according to an embodiment of the present application. As shown in FIG. 4 , the apparatus includes:

The configuration module 40 is used for configuring basic service information and deployment information, wherein the basic service information includes at least a service name indicating the service to be published, and the deployment information includes at least the running location of the service to be published and the number of instances to be started;

A receiving module 42, configured to receive a service release request of the target object, wherein the service release request at least carries the respective identification information corresponding to the multiple target services to be released, and the dependencies of the multiple target services;

A determination module 44, configured to determine the release priority of each target service in the plurality of target services according to the dependencies of the plurality of target services;

The publishing module 46 is configured to publish each target service in batches according to the publishing priority, basic service information and deployment information.

In the microservice publishing apparatus, the configuration module 40 is configured to configure basic service information and deployment information, wherein the basic service information includes at least a service name indicating the service to be published, and the deployment information includes at least the running location of the service to be published and the to-be-launched service. The receiving module 42 is used to receive the service release request of the target object, wherein the service release request at least carries the identification information corresponding to each of the multiple target services to be released, and the dependencies of the multiple target services; the determining module 44 , used to determine the release priority of each target service in the multiple target services according to the dependencies of the multiple target services; the release module 46 is used to release each target service in batches according to the release priority, basic service information and deployment information, so as to achieve The purpose of intelligently releasing the services to be upgraded to their respective operating platforms according to the release priority, simplifying the operation and maintenance work and improving the deployment efficiency, thus realizing the complex logic of the release order is presented in front of the development and operation and maintenance personnel in the form of simple expressions. , and through the system's automatic and intelligent analysis of the technical effect of execution, it solves the problem of high development and operation and maintenance communication costs caused by the completion of the micro-service transformation of the business system, the substantial increase in the number of services, and the release and upgrade of new services through Jenkins. Technical problems such as technical problems such as long release time and inability to meet actual needs.

According to another aspect of the embodiments of the present application, a non-volatile storage medium is also provided, the storage medium includes a stored program, wherein when the program runs, the device where the storage medium is located is controlled to execute any method for publishing microservices.

Specifically, the above-mentioned storage medium is used to store the program instructions of the following functions to realize the following functions:

Configure basic service information and deployment information, where the basic service information includes at least the service name of the service to be published, and the deployment information at least includes the running location of the service to be published and the number of instances to be started; receive a service publication request from the target object, where the service The publishing request carries at least the respective identification information of the multiple target services to be published, and the dependencies of the multiple target services; the publishing priority of each target service in the multiple target services is determined according to the dependencies of the multiple target services; Release priority, service basic information and deployment information Batch release each target service

It should be noted that, in this embodiment, the above storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the above. More specific examples of the above storage media would include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM) or flash memory), fiber optics, compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

In an exemplary embodiment of the present application, a computer program product is also provided, including a computer program, and when the computer program is executed by a processor, any one of the foregoing microservice publishing methods is implemented.

Optionally, the computer program can implement the following steps when executed by the processor:

Configure basic service information and deployment information, where the basic service information includes at least the service name of the service to be published, and the deployment information at least includes the running location of the service to be published and the number of instances to be started; receive a service publication request from the target object, where the service The publishing request carries at least the respective identification information of the multiple target services to be published, and the dependencies of the multiple target services; the publishing priority of each target service in the multiple target services is determined according to the dependencies of the multiple target services; Publish priority, service basic information and deployment information to publish each target service in batches.

According to an embodiment of the present application, an electronic device is provided, the electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions Executed by at least one processor, so that the at least one processor can execute any one of the above-mentioned methods for publishing microservices.

Optionally, the above electronic device may further include a transmission device and an input/output device, wherein the transmission device is connected to the above-mentioned processor, and the input device and the output device are connected to the above-mentioned processor.

FIG. 5 shows a schematic block diagram of an example electronic device 500 that may be used to implement embodiments of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are by way of example only, and are not intended to limit implementations of the application described and/or claimed herein.

As shown in FIG. 5 , the device 500 includes a computing unit 501 that can be executed according to a computer program stored in a read only memory (ROM) 502 or loaded from a storage unit 508 into a random access memory (RAM) 503 Various appropriate actions and handling. In the RAM 503, various programs and data necessary for the operation of the device 500 can also be stored. The computing unit 501 , the ROM 502 , and the RAM 503 are connected to each other through a bus 504 . An input/output (I/O) interface 505 is also connected to bus 504 .

Various components in the device 500 are connected to the I/O interface 505, including: an input unit 506, such as a keyboard, mouse, etc.; an output unit 507, such as various types of displays, speakers, etc.; a storage unit 508, such as a magnetic disk, an optical disk, etc. ; and a communication unit 509, such as a network card, a modem, a wireless communication transceiver, and the like. The communication unit 509 allows the device 500 to exchange information/data with other devices through a computer network such as the Internet and/or various telecommunication networks.

Computing unit 501 may be various general-purpose and/or special-purpose processing components with processing and computing capabilities. Some examples of computing units 501 include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), various specialized artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processing processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 501 executes the various methods and processes described above, such as the publishing method of the microservice. For example, in some embodiments, method XXX may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 508 . In some embodiments, part or all of the computer program may be loaded and/or installed on device 500 via ROM 502 and/or communication unit 509 . When the computer program is loaded into RAM 503 and executed by computing unit 801, one or more steps of the above-described publishing method of microservices may be performed. Alternatively, in other embodiments, the computing unit 501 may be configured to perform the method of microservice publishing by any other suitable means (eg, by means of firmware).

Various implementations of the systems and techniques described herein above may be implemented in digital electronic circuitry, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips system (SOC), load programmable logic device (CPLD), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include being implemented in one or more computer programs executable and/or interpretable on a programmable system including at least one programmable processor that The processor, which may be a special purpose or general-purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device an output device.

Program code for implementing the methods of the present application may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, performs the functions/functions specified in the flowcharts and/or block diagrams. Action is implemented. The program code may execute entirely on the machine, partly on the machine, partly on the machine and partly on a remote machine as a stand-alone software package or entirely on the remote machine or server.

In the context of this application, a machine-readable medium may be a tangible medium that may contain or store the program for use by or in connection with the instruction execution system, apparatus or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), fiber optics, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.

To provide interaction with a user, the systems and techniques described herein may be implemented on a computer having a display device (eg, a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user ); and a keyboard and pointing device (eg, a mouse or trackball) through which a user can provide input to the computer. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (eg, visual feedback, auditory feedback, or tactile feedback); and can be in any form (including acoustic input, voice input, or tactile input) to receive input from the user.

The systems and techniques described herein may be implemented on a computing system that includes back-end components (eg, as a data server), or a computing system that includes middleware components (eg, an application server), or a computing system that includes front-end components (eg, a user's computer having a graphical user interface or web browser through which a user may interact with implementations of the systems and techniques described herein), or including such backend components, middleware components, Or any combination of front-end components in a computing system. The components of the system may be interconnected by any form or medium of digital data communication (eg, a communication network). Examples of communication networks include: Local Area Networks (LANs), Wide Area Networks (WANs), and the Internet.

A computer system can include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server arises by computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, a distributed system server, or a server combined with blockchain.

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

In the above-mentioned embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are only illustrative, for example, the division of units may be a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components may be combined or integrated into Another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of units or modules, and may be in electrical or other forms.

Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed over multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , which includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes .

The above are only the preferred embodiments of the present application. It should be pointed out that for those skilled in the art, some improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as The protection scope of this application.

Claims (10)

1. A micro-service release method is applied to a cloud native environment and comprises the following steps:

configuring service basic information and deployment information, wherein the service basic information at least comprises a service name of a service to be published, and the deployment information at least comprises an operation position of the service to be published and the number of instances to be started;

receiving a service release request of a target object, wherein the service release request at least carries identification information corresponding to a plurality of target services to be released and the dependency relationship of the plurality of target services;

determining the issuing priority of each target service in the target services according to the dependency relationship of the target services;

and releasing each target service in batch according to the release priority, the service basic information and the deployment information.

2. The method according to claim 1, wherein the mass publishing of the target services by the service basic information and the deployment information according to the publishing priority comprises:

detecting whether a target moment is a preset upgrading moment, and reading the service list to be issued under the condition that the target moment is the preset upgrading moment, wherein the service list to be issued comprises: each target service;

inquiring target service basic information and target deployment information corresponding to each target service;

and determining the issuing sequence of each target service according to the issuing priority, and issuing the target service according to the issuing sequence, the target service basic information and the target deployment information.

3. The method according to claim 2, wherein determining a distribution order of each target service according to the distribution priority, and distributing the target service according to the distribution order, the target service basic information, and the target deployment information comprises:

detecting a first target service to be issued currently in the plurality of target services, and judging whether the first target service has a dependent service to obtain a judgment result;

and issuing the first target service according to first target service basic information and first target deployment information corresponding to the first target service under the condition that the judgment result indicates that the first target service does not have the dependent service.

4. The method according to claim 2, wherein determining a distribution order of each target service according to the distribution priority, and distributing the target service according to the distribution order, the target service basic information, and the target deployment information comprises:

detecting a first target service to be issued currently in the plurality of target services, and judging whether the first target service has a dependent service to obtain a judgment result;

issuing the dependent service under the condition that the judgment result indicates that the first target service has the dependent service, wherein the dependent relationship of the dependent service comprises: the system comprises a normal dependency relationship and a strong dependency relationship, wherein the priority of the strong dependency relationship is higher than that of the normal dependency relationship.

5. The method of claim 4, wherein publishing the dependent service comprises:

and detecting whether the dependent service is successfully issued, and stopping issuing the first target service under the condition that the dependent service is unsuccessfully issued.

6. The method of claim 5, wherein the first target service is published if the dependent service publication is successful.

7. The method of any one of claims 3 to 6, wherein in case of a failure of the first target service to publish, the dependent service rolls back to a pre-publication state.

8. A microservice distribution apparatus, comprising:

the system comprises a configuration module, a service management module and a service release module, wherein the configuration module is used for configuring service basic information and deployment information, the service basic information at least comprises a service name indicating a service to be released, and the deployment information at least comprises an operation position of the service to be released and the number of instances to be started;

a receiving module, configured to receive a service publishing request of a target object, where the service publishing request at least carries identification information corresponding to a plurality of target services to be published, and a dependency relationship between the plurality of target services;

the determining module is used for determining the issuing priority of each target service in the target services according to the dependency relationship of the target services;

and the issuing module is used for issuing each target service in batch according to the issuing priority, the service basic information and the deployment information.

9. A non-volatile storage medium, characterized in that the storage medium comprises a stored program, wherein when the program runs, the device where the storage medium is located is controlled to execute the micro-service issuing method according to any one of claims 1 to 7.

10. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the microservice issuing method of any of claims 1-7.

Images