Micro-service starting method and device based on resource configuration, equipment and storage medium

Abstract

The invention relates to a micro-service starting method and device based on resource configuration, equipment and a storage medium, and the method comprises the steps: taking configuration information corresponding to each middleware as a resource for storage, associating the configuration information of the micro-service with the resource according to the identifier of each resource, and when the micro-service is started, starting the middleware according to the identifier of each resource. And according to the resource identifier corresponding to the micro-service, loading target information required for starting the micro-service into the micro-service to start the micro-service. Therefore, when the configuration information of the middleware is modified or changed, the configuration information only needs to be changed once on the resource abstraction layer, the risk of errors and omission is reduced, and the specific configuration information can be obtained through the resource identifier when each micro-service is started / released, so that the situation that the micro-service is failed to start is greatly avoided.

Description

Technical Field

[0001] The present application relates to the field of microservice technology, and in particular to a microservice startup method, device, equipment and storage medium based on resource configuration. Background Art

[0002] Microservice architecture is a cloud-native architecture approach that includes many small, loosely coupled and independently deployable components or services in a single application. There are hundreds of microservices in the system developed under the microservice architecture. Common microservices need to rely on various application software middleware to complete their respective functions. At runtime, microservices create TCP connections and communicate with middleware through the configuration information of each middleware in their configuration files. Since a middleware may be connected to multiple different microservices, and the configuration files of each microservice are scattered in their respective microservices. When the configuration information of these middlewares needs to be changed, it is necessary to manually modify them one by one in the configuration files of the microservices before starting the microservice. However, if the number of modifications is large, it is easy to cause modification errors, and it is not convenient to check and verify, which easily causes the failure of microservice startup.

[0003] Therefore, how to avoid microservice startup failure when the configuration information of the middleware changes has become a technical problem that needs to be solved urgently by those skilled in the art. Summary of the invention

[0004] In view of the above, the present application provides a microservice startup method, device, equipment and storage medium based on resource configuration, which aims to solve the above technical problems.

[0005] In a first aspect, the present application provides a microservice startup method based on resource configuration, the method comprising:

[0006] Save the configuration information corresponding to each middleware as a resource;

[0007] According to the identifier of each resource, associate the configuration information of the microservice with the resource;

[0008] When the microservice is started, target information required for starting the microservice is loaded into the microservice according to a resource identifier corresponding to the microservice, so as to start the microservice according to the target information.

[0009] Preferably, associating the configuration information of the microservice with the resource according to the identifier of each resource includes:

[0010] Assign an identifier to each resource respectively to obtain a resource identifier of each resource;

[0011] Based on resource identification, the configuration information of the microservice is associated with the resources required for the microservice to run.

[0012] Preferably, the associating the configuration information of the microservice with the resources required for the operation of the microservice based on the resource identifier includes:

[0013] Determine the target middleware that the microservice needs to connect to;

[0014] Determine the target resource identifier corresponding to the target middleware;

[0015] Associate the configuration information of the microservice with the resource corresponding to the target resource identifier.

[0016] Preferably, the step of loading target information required for starting the microservice into the microservice according to the resource identifier corresponding to the microservice includes:

[0017] Determine the middleware configuration information corresponding to the microservice according to the resource identifier corresponding to the microservice;

[0018] The middleware configuration information corresponding to the microservice is loaded into the microservice as target information.

[0019] Preferably, starting the microservice according to the target information includes:

[0020] According to the target information, a connection pool, a sender, and a receiver corresponding to the middleware are created to start the microservice.

[0021] Preferably, the middleware includes a database and / or a message queue.

[0022] In a second aspect, the present application provides a microservice startup device based on resource configuration, the device comprising:

[0023] Saving module: used to save the configuration information corresponding to each middleware as a resource;

[0024] Association module: used to associate the configuration information of microservices with resources according to the identifier of each resource;

[0025] Startup module: used for loading target information required for starting the microservice into the microservice according to the resource identifier corresponding to the microservice when the microservice is started, so as to start the microservice according to the target information.

[0026] In a third aspect, the present application provides an electronic device, including a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0027] Memory, used to store computer programs;

[0028] The processor is used to implement the microservice startup method based on resource configuration as described in any embodiment of the first aspect when executing the program stored in the memory.

[0029] In a fourth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the microservice startup method based on resource configuration as described in any embodiment of the first aspect is implemented.

[0030] The above technical solution provided by the embodiment of the present application has the following advantages compared with the prior art:

[0031] The present application saves the configuration information corresponding to each middleware as a resource, associates the configuration information of the microservice with the resource according to the identifier of each resource, and when the microservice is started, loads the target information required for starting the microservice into the microservice according to the resource identifier corresponding to the microservice to start the microservice, so that when the configuration information of the middleware is modified or changed, it only needs to be changed once at the resource abstraction layer, reducing the risk of errors and omissions, and each microservice can obtain the specific configuration information through the resource identifier when starting / releasing, thereby greatly avoiding the failure of microservice startup. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0033] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0034] Figure 1 This is a flow chart of an embodiment of a microservice startup method based on resource configuration of the present application;

[0035] Figure 2 This is a module diagram of an embodiment of a microservice startup device based on resource configuration of the present application;

[0036] Figure 3 A schematic diagram of an electronic device embodiment of the present application;

[0037] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0038] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0039] The disclosure below provides many different embodiments or examples to realize the different structures of the present application. In order to simplify the disclosure of the present application, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present application. In addition, the present application can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0040] This application provides a microservice startup method based on resource configuration. Figure 1 , which is a method flow diagram of an embodiment of a method for starting a microservice based on resource configuration in the present application. The method can be executed by an electronic device, and the electronic device can be implemented by software and / or hardware. The method for starting a microservice based on resource configuration includes:

[0041] Step S10: save the configuration information corresponding to each middleware as a resource;

[0042] Step S20: according to the identifier of each resource, the configuration information of the microservice is associated with the resource;

[0043] Step S30: when the microservice is started, target information required for starting the microservice is loaded into the microservice according to the resource identifier corresponding to the microservice, so as to start the microservice according to the target information.

[0044] There are hundreds of microservices in the system developed under the microservice architecture. Common microservices need to rely on various application software middleware to complete their respective functions. For example, they need to rely on middleware such as relational database, cache service, file storage service, message queue service, etc. When the microservice is running, it creates a TCP connection to communicate with the middleware through the configuration information of each middleware in its configuration file. Among them, the middleware includes a database and / or a message queue.

[0045] Usually, a middleware is connected to multiple microservices, and the configuration files of each microservice are scattered in each microservice. For example, a complex trading system has hundreds of microservices, and dozens of microservices need to connect to the same relational database and message queue. When the configuration information of these middlewares (such as server address, port, timeout, etc.) needs to be changed, it is necessary to manually modify them one by one in the configuration files of the microservices. If the number of modifications is large, it is easy to cause modification errors and it is not convenient to check and verify.

[0046] To this end, the embodiment of the present application defines a resource abstraction layer, and saves the configuration information of each middleware such as database, message queue, storage, etc. as a resource, and sets a unique resource ID for each resource. Each microservice associates the resources it needs through the resource ID, but the microservice itself does not need to know the specific configuration information contained in this resource. When the configuration information of the middleware needs to be modified, it only needs to be changed once in the resource abstraction layer, reducing the risk of errors and omissions. The specific configuration information can be obtained through the resource ID when each microservice is started / published. Specifically, by defining a resource abstraction layer, the configuration information corresponding to each middleware is saved as a resource. For example, there is a relational database with an IP address of 192.168.78.66, a port of 3306, and a database name of account_sys. The database is used as a resource and an ID of "db1" is assigned to it. If the IP address, port, and database name of a relational database are different from the database "db1", it represents another resource.

[0047] Each microservice can declare a reference to the db1 resource, so that db1 can be resolved into specific connection information. The microservice can then establish a connection with the relational database represented by db1 through the specific connection information.

[0048] After the configuration information corresponding to each middleware is saved as a resource, the configuration information of the microservice is associated with the resource according to the identifier of each resource. Specifically, according to the identifier of each resource, the configuration information of the microservice is associated with the resource, including:

[0049] Assign an identifier to each resource respectively to obtain a resource identifier of each resource;

[0050] Based on resource identification, the configuration information of the microservice is associated with the resources required for the microservice to run.

[0051] By defining multiple resources and assigning a unique ID to each resource, the microservice declares and references this resource ID according to its own business needs. In the process of service parsing configuration files, a custom parser is added to complete the process of replacing the resource ID with specific configuration information. The subsequent microservice startup framework will automatically complete the middleware connection based on these specific configuration information.

[0052] Furthermore, the configuration information of the microservice is associated with the resources required for the operation of the microservice based on the resource identifier, including:

[0053] Determine the target middleware that the microservice needs to connect to;

[0054] Determine the target resource identifier corresponding to the target middleware;

[0055] Associate the configuration information of the microservice with the resource corresponding to the target resource identifier.

[0056] For example, if there are three middlewares, the first middleware has an IP of 192.168.78.11 and a port of 3306. The database name is account_sys and the product type is MySQL relational database. It is defined as a resource and its assigned resource ID is db1.

[0057] The second middleware is a cache service with a product type of Redis and an IP address of 192.168.78.13 and a port number of 6379. It is defined as a resource and its resource ID is cache1.

[0058] The third middleware is a message middleware with IP address 192.168.78.23, port 32264, virtual host dev, product type RabbitMQ. It is defined as a resource and its resource ID is mq1. Assuming that there is a microservice that processes order transactions, and this microservice needs to rely on the above three middlewares, then fill in "application.database.resource-id=db1", "application.redis.resource-id=cache1", and "application.mq.resource-id=mq1" in the configuration file of this microservice to establish an association, without filling in the specific configuration information of each middleware. It should be noted that for online order transaction microservices, it is generally necessary to configure relational databases and message queue middleware. For file storage microservices, it is generally necessary to configure object storage middleware. For management platform microservices, their own HTTP port information, key information, relational database connection information, etc. are usually configured.

[0059] When the microservice is started, the configuration file parser is loaded for processing. The parser can be implemented by code. When the microservice is started, the configuration file parser loads the target information required for microservice startup into the microservice according to the resource ID, so as to start the microservice according to the target information. Specifically, according to the resource identifier corresponding to the microservice, the target information required for microservice startup is loaded into the microservice, including:

[0060] Determine the middleware configuration information corresponding to the microservice according to the resource identifier corresponding to the microservice;

[0061] The middleware configuration information corresponding to the microservice is loaded into the microservice as target information.

[0062] In the current microservice framework design, microservice startup is carried out in steps. Before creating each class object, the configuration file will be parsed first, and the object communicating with the middleware will be created through the configuration in the configuration file. Since the middleware is saved as a resource in advance and the corresponding resource ID is assigned in this embodiment, when parsing the configuration file, it can be extended according to the configuration file processing interface opened by the microservice framework, and the middleware configuration information corresponding to the ID can be found through the resource ID, and then the middleware configuration information is added as the target information to the microservice startup context, so that the microservice framework can create the middleware communication object according to the filled middleware configuration information in the subsequent process.

[0063] Further, starting the microservice according to the target information includes:

[0064] According to the target information, the connection pool, sender and receiver corresponding to the middleware are created to start the microservice. The microservice creates corresponding database connection pool, message queue sender / receiver and other objects according to various configuration information to complete the startup of the microservice.

[0065] Reference Figure 2 , which is a schematic diagram of functional modules of a microservice startup device 100 based on resource configuration in the present application.

[0066] The resource configuration-based microservice startup device 100 described in the present application can be installed in an electronic device. According to the functions implemented, the resource configuration-based microservice startup device 100 may include a storage module 110, an association module 120 and a startup module 130. The module described in the present application can also be referred to as a unit, which refers to a series of computer program segments that can be executed by an electronic device processor and can complete fixed functions, which are stored in the memory of the electronic device.

[0067] In this embodiment, the functions of each module / unit are as follows:

[0068] Saving module 110: used to save the configuration information corresponding to each middleware as a resource;

[0069] Association module 120: used to associate the configuration information of the microservice with the resource according to the identifier of each resource;

[0070] The startup module 130 is used to load the target information required for starting the microservice into the microservice according to the resource identifier corresponding to the microservice when the microservice is started, so as to start the microservice according to the target information.

[0071] In one embodiment, associating the configuration information of the microservice with the resource according to the identifier of each resource includes:

[0072] Assign an identifier to each resource respectively to obtain a resource identifier of each resource;

[0073] Based on resource identification, the configuration information of the microservice is associated with the resources required for the microservice to run.

[0074] In one embodiment, associating the configuration information of the microservice with the resources required for the operation of the microservice based on the resource identifier includes:

[0075] Determine the target middleware that the microservice needs to connect to;

[0076] Determine the target resource identifier corresponding to the target middleware;

[0077] Associate the configuration information of the microservice with the resource corresponding to the target resource identifier.

[0078] In one embodiment, the step of loading target information required for starting the microservice into the microservice according to the resource identifier corresponding to the microservice includes:

[0079] Determine the middleware configuration information corresponding to the microservice according to the resource identifier corresponding to the microservice;

[0080] The middleware configuration information corresponding to the microservice is loaded into the microservice as target information.

[0081] In one embodiment, starting the microservice according to the target information includes:

[0082] According to the target information, a connection pool, a sender, and a receiver corresponding to the middleware are created to start the microservice.

[0083] In one embodiment, the middleware includes a database and / or a message queue.

[0084] Reference Figure 3, which is a schematic diagram of a preferred embodiment of the electronic device of the present application.

[0085] The electronic device includes a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other via the communication bus 114;

[0086] The memory 113 is used to store computer programs, for example, a microservice startup program based on resource configuration;

[0087] Among them, the processor 111 can be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 111 is generally used to control the overall operation of the electronic device, such as performing data interaction or communication-related control and processing. In this embodiment, the processor 111 is used to run the program code stored in the memory 113 or process data, such as running the program code of the microservice startup program based on resource configuration.

[0088] The communication interface 112 may optionally include a standard wired interface, a wireless interface (such as a WI-FI interface), and the communication interface 112 may also be used to establish a communication connection between the electronic device and other electronic devices.

[0089] The memory 113 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 113 can be an internal storage unit of the electronic device, such as a hard disk or memory of the electronic device. In other embodiments, the memory 113 can also be an external storage device of the electronic device, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped with the electronic device. Of course, the memory 113 can also include both the internal storage unit of the electronic device and its external storage device. In this embodiment, the memory 11 is generally used to store the operating system and various computer programs installed in the electronic device, such as the program code of the microservice startup program based on resource configuration, etc. In addition, the memory 113 can also be used to temporarily store various types of data that have been output or are to be output.

[0090] Figure 3 Only an electronic device having components 111 - 114 is shown, but it is understood that implementing all of the components shown is not a requirement, and more or fewer components may alternatively be implemented.

[0091] In one embodiment of the present application, the processor 111 is used to execute the program stored in the memory 113 to implement the microservice startup method based on resource configuration provided by any of the aforementioned method embodiments, including:

[0092] Save the configuration information corresponding to each middleware as a resource;

[0093] According to the identifier of each resource, associate the configuration information of the microservice with the resource;

[0094] When the microservice is started, target information required for starting the microservice is loaded into the microservice according to a resource identifier corresponding to the microservice, so as to start the microservice according to the target information.

[0095] For a detailed description of the above steps, please refer to the above Figure 1 Description of a flowchart of an embodiment of a microservice startup method based on resource configuration.

[0096] In addition, the embodiment of the present application also proposes a computer-readable storage medium, which may be non-volatile or volatile. The computer-readable storage medium includes a data storage area and a program storage area, and the program storage area stores a microservice startup program based on resource configuration. When the microservice startup program based on resource configuration is executed by a processor, the following operations are implemented:

[0097] Save the configuration information corresponding to each middleware as a resource;

[0098] According to the identifier of each resource, associate the configuration information of the microservice with the resource;

[0099] When the microservice is started, target information required for starting the microservice is loaded into the microservice according to a resource identifier corresponding to the microservice, so as to start the microservice according to the target information.

[0100] The specific implementation of the computer-readable storage medium of the present application is roughly the same as the specific implementation of the above-mentioned microservice startup method based on resource configuration, and will not be repeated here.

[0101] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0102] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0103] It should be noted that the descriptions involving "first", "second", etc. in this application are only for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in this field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0104] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0105] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. A microservice startup method based on resource configuration, characterized in that: The method comprises: Save the configuration information corresponding to each middleware as a resource; According to the identifier of each resource, associate the configuration information of the microservice with the resource; When the microservice is started, target information required for starting the microservice is loaded into the microservice according to a resource identifier corresponding to the microservice, so as to start the microservice according to the target information.

2. The microservice startup method based on resource configuration as claimed in claim 1, characterized in that: According to the identifier of each resource, the configuration information of the microservice is associated with the resource, including: Assign an identifier to each resource respectively to obtain a resource identifier of each resource; Based on resource identification, the configuration information of the microservice is associated with the resources required for the microservice to run.

3. The microservice startup method based on resource configuration as described in claim 2, characterized in that: The method of associating the configuration information of the microservice with the resources required for the operation of the microservice based on the resource identifier includes: Determine the target middleware that the microservice needs to connect to; Determine the target resource identifier corresponding to the target middleware; Associate the configuration information of the microservice with the resource corresponding to the target resource identifier.

4. The microservice startup method based on resource configuration as claimed in claim 1, characterized in that: The step of loading target information required for starting the microservice into the microservice according to the resource identifier corresponding to the microservice includes: Determine the middleware configuration information corresponding to the microservice according to the resource identifier corresponding to the microservice; The middleware configuration information corresponding to the microservice is loaded into the microservice as target information.

5. The microservice startup method based on resource configuration as claimed in claim 1, characterized in that: The starting the microservice according to the target information includes: According to the target information, a connection pool, a sender, and a receiver corresponding to the middleware are created to start the microservice.

6. The microservice startup method based on resource configuration according to claim 1, characterized in that: The middleware includes a database and / or a message queue.

7. A microservice startup device based on resource configuration, characterized in that: The device comprises: Saving module: used to save the configuration information corresponding to each middleware as a resource; Association module: used to associate the configuration information of microservices with resources according to the identifier of each resource; Startup module: used for loading target information required for starting the microservice into the microservice according to the resource identifier corresponding to the microservice when the microservice is started, so as to start the microservice according to the target information.

8. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; The processor is used to execute the program stored in the memory, and implements the following steps: Save the configuration information corresponding to each middleware as a resource; According to the identifier of each resource, associate the configuration information of the microservice with the resource; When the microservice is started, target information required for starting the microservice is loaded into the microservice according to a resource identifier corresponding to the microservice, so as to start the microservice according to the target information.

9. The electronic device according to claim 8, characterized in that: According to the identifier of each resource, the configuration information of the microservice is associated with the resource, including: Assign an identifier to each resource respectively to obtain a resource identifier of each resource; Based on resource identification, the configuration information of the microservice is associated with the resources required for the microservice to run.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the microservice startup method based on resource configuration according to any one of claims 1 to 6 is implemented.

Images