CN111541561A - Microservice configuration information management system, microservice configuration information management method, microservice configuration information management server, and storage medium - Google Patents
Microservice configuration information management system, microservice configuration information management method, microservice configuration information management server, and storage medium Download PDFInfo
- Publication number
- CN111541561A CN111541561A CN202010274081.XA CN202010274081A CN111541561A CN 111541561 A CN111541561 A CN 111541561A CN 202010274081 A CN202010274081 A CN 202010274081A CN 111541561 A CN111541561 A CN 111541561A
- Authority
- CN
- China
- Prior art keywords
- micro
- service
- configuration information
- target
- microservice
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention provides a micro-service configuration information management system, a method, a server and a storage medium, wherein the system comprises: a micro service management platform, an API gateway and a Redis; the micro service management platform receives the micro service configuration information and issues the micro service configuration information to the API gateway; the API gateway receives the micro-service configuration information and stores the micro-service configuration information to Redis; redis determines a target micro service from a plurality of micro services controlled by the micro service management platform, and pushes a notification of micro service configuration information change to the target micro service, so that the target micro service acquires the micro service configuration information and changes the micro service configuration information local to the target micro service. Therefore, the micro-service configuration information is persistently stored through Redis, the target micro-service is informed to acquire the micro-service configuration information, the local micro-service configuration information is changed, the micro-service configuration information can be changed under the condition that the micro-service is normally operated, and the influence on the micro-service quality is avoided.
Description
Technical Field
The embodiment of the invention relates to the technical field of micro services, in particular to a micro service configuration information management system, a method, a server and a storage medium.
Background
With the increasing penetration of the mobile internet, more and more companies and enterprises are gradually starting to face the internet and migrating customer-facing services and businesses to the online. As the number of customers continues to increase in developing these online services, the architecture of the service level is constantly evolving. From the early single application architecture to the micro-service architecture, clustering and distribution become standard technology.
In the process of constructing the basic platform of the micro service structure, the API gateway is one of the indispensable core components. The API gateway provides a uniform interface for a set of microservices so that the client does not need to know all the details inside the microservices. Among them, Spring Cloud Gateway (SCG) is an API (application programming Interface) Gateway which is widely used at present.
For SCG, management of micro service configuration information is vulnerable, and a persistent storage scheme for micro service configuration information is not provided, the micro service configuration information is from initialization, i.e. configuration file (e.g. application. yml), and if SCG stops running, the micro service configuration information in the corresponding configuration file disappears. When a corresponding server in the micro service is down, the micro service configuration information in the configuration file needs to be modified to restart the SCG, so that the restarted server loads the micro service configuration information to provide the micro service again, and the micro service is easily interrupted in the period, thereby affecting the quality of the micro service.
Disclosure of Invention
In order to solve the technical problem that when a corresponding server in a micro service is down, micro service configuration information in a configuration file needs to be modified to restart an SCG, so that a restarted server loads the micro service configuration information and provides the micro service again, interruption of the micro service is easily caused during the process, and the quality of the micro service is affected, embodiments of the present invention provide a system, a method, a server, and a storage medium for managing the micro service configuration information. The specific technical scheme is as follows:
in a first aspect of the embodiments of the present invention, a micro service configuration information management system is provided, where the system includes: a micro service management platform, an API gateway and a Redis;
the micro service management platform receives micro service configuration information and issues the micro service configuration information to the API gateway;
the API gateway receives the micro-service configuration information issued by the micro-service management platform and stores the micro-service configuration information to the Redis;
the Redis determines a target micro service from a plurality of micro services controlled by the micro service management platform, and pushes a notification of micro service configuration information change to the target micro service, so that the target micro service acquires the micro service configuration information and changes the local micro service configuration information of the target micro service.
In an optional embodiment, the determining, by the Redis, a target microservice from a plurality of microservices managed and controlled by the microservice management platform includes:
the Redis acquires a preset micro-service subscription list;
for any micro service managed and controlled by the micro service management platform, the Redis judges whether the micro service exists in the micro service subscription list or not;
and if the micro service exists in the micro service subscription list, the Redis determines that the micro service is the target micro service.
In an optional embodiment, the acquiring, by the target microservice, the microservice configuration information, and changing the microservice configuration information local to the target microservice includes:
and the target micro service acquires the micro service configuration information through a real-time timer configured by Spring Boot, and changes the local micro service configuration information of the target micro service.
In an optional embodiment, the acquiring, by the target microservice, the microservice configuration information, and changing the microservice configuration information local to the target microservice includes:
the target micro service acquires the micro service configuration information;
the target micro service judges whether the micro service configuration information is suitable for the target micro service;
and if the micro-service configuration information is suitable for the target micro-service, the target micro-service utilizes the micro-service configuration information to change the local micro-service configuration information of the target micro-service.
In an optional embodiment, the determining, by the target microservice, whether the microservice configuration information is applicable to itself includes:
the target micro service analyzes a micro service identifier carried in the micro service configuration information;
the target micro service judges whether the micro service identification is consistent with the self identification;
if the microservice configuration information is suitable for the microservice, the target microservice changes the microservice configuration information local to the target microservice by using the microservice configuration information, and the change comprises the following steps:
and if the micro-service identifier is consistent with the self identifier, the target micro-service utilizes the micro-service configuration information to change the local micro-service configuration information of the target micro-service.
In an optional embodiment, the system further comprises:
and if the micro-service identifier is not consistent with the self identifier, the target micro-service deletes the micro-service configuration information.
In an optional embodiment, the determining, by the target microservice, whether the microservice configuration information is applicable to itself includes:
extracting micro-service configuration original information in the micro-service configuration information by the target micro-service;
the target micro service judges whether the micro service configuration original information is consistent with the micro service configuration information of the target micro service;
if the microservice configuration information is suitable for the microservice, the target microservice changes the microservice configuration information local to the target microservice by using the microservice configuration information, and the change comprises the following steps:
and if the original micro-service configuration information is consistent with the local micro-service configuration information of the target micro-service, the target micro-service utilizes the micro-service configuration information to change the local micro-service configuration information of the target micro-service.
In an optional embodiment, the system further comprises:
and if the original micro-service configuration information is not consistent with the local micro-service configuration information of the target micro-service, the target micro-service deletes the micro-service configuration information.
In a second aspect of the embodiments of the present invention, there is also provided a method for managing microservice configuration information, which is applied to an API gateway, and the method includes:
receiving micro service configuration information issued by a micro service management platform;
storing the micro-service configuration information to Redis, so that the Redis determines a target micro-service from a plurality of micro-services managed and controlled by the micro-service management platform, and pushes a notification of micro-service configuration information change to the target micro-service;
the notification of the change of the microservice configuration information is used for enabling the target microservice to acquire the microservice configuration information and change the microservice configuration information local to the target microservice.
In a third aspect of the embodiments of the present invention, there is further provided a server, including a processor, a communication interface, a memory, and a communication bus, where the processor and the communication interface complete communication between the memory and the processor through the communication bus;
a memory for storing a computer program;
and the processor is used for realizing the management method of the microservice configuration information in the second aspect when executing the program stored in the memory.
In a fourth aspect of the embodiments of the present invention, there is also provided a storage medium having instructions stored therein, which when run on a computer, cause the computer to execute the micro-service configuration information management method described in the second aspect above.
In a fifth aspect of the embodiments of the present invention, there is also provided a computer program product containing instructions, which when run on a computer, causes the computer to execute the micro-service configuration information management method described in the second aspect above.
According to the technical scheme provided by the embodiment of the invention, the micro-service configuration information is received by the micro-service management platform and is issued to the API gateway, the API gateway receives the micro-service configuration information and stores the micro-service configuration information to Redis, the Redis determines a target micro-service from a plurality of micro-services controlled by the micro-service management platform, and pushes a notification of micro-service configuration information change to the target micro-service, so that the target micro-service acquires the micro-service configuration information and changes the local micro-service configuration information. Therefore, the micro-service configuration information is persistently stored through Redis, the target micro-service is informed to acquire the micro-service configuration information, the local micro-service configuration information is changed, the micro-service configuration information can be changed under the condition that the micro-service is normally operated, and the influence on the micro-service quality is avoided.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic structural diagram of a microservice configuration information management system shown in an embodiment of the present invention;
fig. 2 is an interaction flow diagram of a method for managing microservice configuration information in an embodiment of the present invention;
FIG. 3 is a schematic interaction flow diagram illustrating another management method for microservice configuration information according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a microservice configuration information management apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a server shown in the embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.
In an embodiment of the present invention, a micro service configuration information management system is provided, where the micro service configuration information management system includes: the system comprises a micro service management platform, an API gateway, and a Redis, wherein the micro service management platform manages a plurality of micro services, and a connection relationship between the micro service management platform, the API gateway, the Redis, and the plurality of micro services may be as shown in fig. 1.
Based on the micro-service configuration information management system shown in fig. 1, the micro-service configuration information is persistently stored through Redis, a target micro-service is notified to obtain the micro-service configuration information, the local micro-service configuration information is changed, the micro-service configuration information can be changed under the condition that the micro-service is normally operated, and the influence on the micro-service quality is avoided.
Based on the management system of the micro service configuration information shown in fig. 1, as shown in fig. 2, an interaction flow diagram of a management method of the micro service configuration information provided in an embodiment of the present invention is shown, and the method specifically includes the following steps:
s201, the micro service management platform receives micro service configuration information and issues the micro service configuration information to the API gateway;
for the micro-service management platform, a user can configure micro-service configuration information on the micro-service management platform, that is, configure micro-service configuration information for a certain micro-service.
In the embodiment of the invention, the micro-service management platform can receive micro-service configuration information configured by a user, namely micro-service configuration information configured by the user aiming at a certain micro-service.
The micro service configuration information may include a micro service IP address, a micro service port, a micro service name, a micro service ID, and the like, which is not limited in the embodiment of the present invention.
For example, in the embodiment of the present invention, the micro service management platform may receive micro service configuration information configured by a user for the micro service a, receive micro service configuration information configured by the user for the micro service B, and receive micro service configuration information configured by the user for the micro service C.
For the received micro-service configuration information, the micro-service management platform in the embodiment of the present invention may issue the micro-service configuration information to the API gateway. The API Gateway may be a Spring Cloud Gateway (SCG), which is not limited in this embodiment of the present invention.
S202, the API gateway receives the micro service configuration information issued by the micro service management platform and stores the micro service configuration information to the Redis;
for the micro service configuration information issued by the micro service management platform, the API gateway in the embodiment of the present invention may receive the micro service configuration information, and may store the micro service configuration information to the Redis.
For Remote Dictionary service (Redis), the system is an open source log-type and Key-Value database which is written by using ANSIC language, supports network, can be based on memory and can also be persistent, and provides API of multiple languages.
For example, for micro-service configuration information 1 for micro-service a, the API gateway may receive the micro-service configuration information 1 and store the micro-service configuration information 1 to Redis.
S203, the Redis determines a target micro service from a plurality of micro services controlled by the micro service management platform, and pushes a notification of micro service configuration information change to the target micro service, so that the target micro service acquires the micro service configuration information and changes the local micro service configuration information of the target micro service.
For the Redis, the micro service configuration information is locally stored at this time, which means that the micro service configuration information needs to be changed, and a target micro service may be determined from a plurality of micro services managed and controlled by the micro service management platform, and a notification of the change of the micro service configuration information may be pushed to the target micro service.
For the target micro service, after receiving the notification of the change of the micro service configuration information pushed by the Redis, the micro service configuration information may be acquired from the Redis, and the local micro service configuration information may be changed, that is, the local micro service configuration information may be updated by using the micro service configuration information.
For example, for Redis, in which micro-service configuration information is stored locally at this time, which means that the micro-service configuration information needs to be changed, a target micro-service a and a target micro-service b may be determined from a plurality of micro-services (micro-service a, micro-service b, and micro-service c) managed by the micro-service management platform, and a notification of the change of the micro-service configuration information may be pushed to the target micro-service a and the target micro-service b;
for the target micro service a and the target micro service b, after receiving the notification of the change of the micro service configuration information pushed by the Redis, the micro service configuration information can be acquired from the Redis, and the local micro service configuration information can be changed.
Through the above description of the technical solution provided by the embodiment of the present invention, the micro service management platform receives the micro service configuration information and issues the micro service configuration information to the API gateway, the API gateway receives the micro service configuration information and stores the micro service configuration information to the Redis, the Redis determines a target micro service from a plurality of micro services managed by the micro service management platform, and pushes a notification of micro service configuration information change to the target micro service, so that the target micro service obtains the micro service configuration information and changes the local micro service configuration information. Therefore, the micro-service configuration information is persistently stored through Redis, the target micro-service is informed to acquire the micro-service configuration information, the local micro-service configuration information is changed, the micro-service configuration information can be changed under the condition that the micro-service is normally operated, and the influence on the micro-service quality is avoided.
As shown in fig. 3, an interaction flow diagram of another management method for microservice configuration information provided in an embodiment of the present invention includes the following steps:
s301, the micro service management platform receives micro service configuration information and issues the micro service configuration information to the API gateway;
in the embodiment of the present invention, this step is similar to the step S201 described above, and details of the embodiment of the present invention are not repeated herein.
S302, the API gateway receives the micro service configuration information issued by the micro service management platform and stores the micro service configuration information to the Redis;
in the embodiment of the present invention, this step is similar to the step S202, and the details of the embodiment of the present invention are not repeated herein.
S303, the Redis acquires a preset micro-service subscription list;
for Redis, at this time, the micro service configuration information is locally stored, which means that there is a change in the micro service configuration information, and it is necessary to determine a target micro service from a plurality of micro services managed by the micro service management platform.
According to the embodiment of the invention, the micro-service subscription list can be preset according to the subscription capability of Redis, and for the micro-services existing in the micro-service subscription list, the notification of the change of the micro-service configuration information can be pushed to the micro-services, so that the Redis can obtain the preset micro-service subscription list.
S304, for any micro service managed and controlled by the micro service management platform, the Redis judges whether the micro service exists in the micro service subscription list;
for the preset micro-service subscription list acquired by the Redis, the Redis judges whether the micro-service exists in the micro-service subscription list or not for any micro-service managed and controlled by the micro-service management platform.
For example, for micro service a, micro service B, and micro service C managed by the micro service management platform, Redis determines whether the micro service a exists in the micro service subscription list, Redis determines whether the micro service B exists in the micro service subscription list, and Redis determines whether the micro service C exists in the micro service subscription list.
S305, if the micro service exists in the micro service subscription list, the Redis determines that the micro service is a target micro service;
for any micro service managed by the micro service management platform, if the micro service exists in a micro service subscription list, Redis determines that the micro service is a target micro service.
For example, for micro service a, micro service B, and micro service C managed by the micro service management platform, if micro service a, micro service B, and micro service C exist in the micro service subscription list, respectively, Redis determines that micro service a, micro service B, and micro service C are target micro services.
S306, the Redis pushes a notification of micro-service configuration information change to the target micro-service, so that the target micro-service acquires the micro-service configuration information and changes the micro-service configuration information local to the target micro-service.
For a target microservice determined by Redis as described above, Redis may push a notification of microservice configuration information change to the target microservice. For the target micro service, after receiving the notification of the change of the micro service configuration information, the micro service configuration information can be acquired from the Redis through a real-time timer configured by the Spring Boot, and the local micro service configuration information is changed.
Wherein, for the micro service configuration information, because the micro service configuration information is applicable to a certain micro service, for the target micro service, the micro service configuration information is obtained from Redis, and whether the micro service configuration information is applicable to the micro service is judged.
If the micro-service configuration information is suitable for the target micro-service, the target micro-service can change the local micro-service configuration information by using the micro-service configuration information.
If the micro-service configuration information is not applicable to itself, the target micro-service may delete the micro-service configuration information.
Specifically, in the embodiment of the present invention, the target micro service may specifically determine whether the micro service configuration information is applicable to itself through the following manner:
in the method 1, the target micro service analyzes the micro service identifier carried in the micro service configuration information, judges whether the micro service identifier is consistent with the self identifier, if the micro service identifier is consistent with the self identifier, the micro service configuration information is determined to be suitable for the self, and then the local micro service configuration information can be changed by using the micro service configuration information, if the micro service identifier is not consistent with the self identifier, the micro service configuration information is determined not to be suitable for the self, and then the micro service configuration information can be deleted.
For example, as shown in table 1 below, the micro service configuration information may include a micro service identifier carried in the micro service configuration information.
TABLE 1
The target micro service a analyzes the micro service identifier a carried in the micro service configuration information 1, judges that the micro service identifier a is consistent with the self identifier a, can determine that the micro service configuration information 1 is suitable for the self, and can further change the local micro service configuration information by using the micro service configuration information 1.
For another example, for the micro service configuration information 1, the target micro service b analyzes the micro service identifier a carried in the micro service configuration information 1, determines that the micro service identifier a is not consistent with the self identifier b, may determine that the micro service configuration information 1 is not applicable to itself, and may delete the micro service configuration information 1.
Mode 2, the target micro service extracts micro service configuration original information in the micro service configuration information, judges whether the micro service configuration original information is consistent with micro service configuration information local to the target micro service, if the micro service configuration original information is consistent with the micro service configuration information local to the target micro service, the micro service configuration information is determined to be applicable to itself, and then the micro service configuration information can be used for changing the local micro service configuration information, if the micro service configuration original information is not consistent with the micro service configuration information local to the target micro service, the micro service configuration information is determined not to be applicable to itself, and then the micro service configuration information can be deleted.
For example, for the micro service configuration information 3, which may include micro service configuration original information and micro service configuration target information, the following table 2 may be used.
| Microservice configuration primitive information | Microservice configuration target information |
| Micro service IP address: 192.168.1.1 | Micro service IP address: 192.168.1.2 |
| Micro-service port: 8080 | Micro-service port: 8080 |
| Name of micro service: a is | Name of micro service: a is |
TABLE 2
The micro service configuration original information in the micro service configuration information 3 should be consistent with the micro service configuration information local to a certain micro service.
For the target micro service a, extracting the micro service configuration original information in the micro service configuration information 3, as shown in the above table 1, judging that the micro service configuration original information is consistent with the local micro service configuration information of the target micro service, and thus, it can be determined that the micro service configuration information 3 is suitable for itself, and further, the local micro service configuration information can be changed by using the micro service configuration information 3.
For the target micro service b, extracting the micro service configuration original information in the micro service configuration information 3, as shown in table 1, judging that the micro service configuration original information is not consistent with the local micro service configuration information of the target micro service, and determining that the micro service configuration information 3 is not suitable for itself, and further deleting the micro service configuration information 3.
Here, the embodiments of the present invention describe, from a single-side perspective, respective steps performed by the micro service management platform, the API gateway, and the Redis:
the micro service management platform receives micro service configuration information and issues the micro service configuration information to the API gateway;
the API gateway receives the micro-service configuration information issued by the micro-service management platform and stores the micro-service configuration information to the Redis;
the Redis determines a target micro service from a plurality of micro services controlled by the micro service management platform, and pushes a notification of micro service configuration information change to the target micro service, so that the target micro service acquires the micro service configuration information and changes the local micro service configuration information of the target micro service.
Corresponding to the foregoing method embodiment, an embodiment of the present invention further provides an apparatus for managing microservice configuration information, as shown in fig. 4, where the apparatus is applied to an API gateway, and the apparatus may include: an information receiving module 410 and an information storing module 420.
An information receiving module 410, configured to receive micro service configuration information issued by a micro service management platform;
an information storage module 420, configured to store the microservice configuration information to a Redis, so that the Redis determines a target microservice from a plurality of microservices managed and controlled by the microservice management platform, and pushes a notification of microservice configuration information change to the target microservice;
the notification of the change of the microservice configuration information is used for enabling the target microservice to acquire the microservice configuration information and change the microservice configuration information local to the target microservice.
The embodiment of the present invention further provides a server, as shown in fig. 5, including a processor 51, a communication interface 52, a memory 53 and a communication bus 54, where the processor 51, the communication interface 52, and the memory 53 complete mutual communication through the communication bus 54,
a memory 53 for storing a computer program;
the processor 51 is configured to implement the following steps when executing the program stored in the memory 53:
receiving micro service configuration information issued by a micro service management platform; storing the micro-service configuration information to Redis, so that the Redis determines a target micro-service from a plurality of micro-services managed and controlled by the micro-service management platform, and pushes a notification of micro-service configuration information change to the target micro-service; the notification of the change of the microservice configuration information is used for enabling the target microservice to acquire the microservice configuration information and change the microservice configuration information local to the target microservice.
The communication bus mentioned in the above server may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the server and other devices.
The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In another embodiment of the present invention, a storage medium is further provided, where instructions are stored, and when the storage medium runs on a computer, the storage medium causes the computer to execute the micro service configuration information management method in any one of the above embodiments.
In yet another embodiment of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method for managing microservice configuration information as described in any of the above embodiments.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a storage medium or transmitted from one storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (11)
1. A microservice configuration information management system, the system comprising: a micro service management platform, an API gateway and a Redis;
the micro service management platform receives micro service configuration information and issues the micro service configuration information to the API gateway;
the API gateway receives the micro-service configuration information issued by the micro-service management platform and stores the micro-service configuration information to the Redis;
the Redis determines a target micro service from a plurality of micro services controlled by the micro service management platform, and pushes a notification of micro service configuration information change to the target micro service, so that the target micro service acquires the micro service configuration information and changes the local micro service configuration information of the target micro service.
2. The system of claim 1, wherein the Redis determines a target microservice from a plurality of microservices managed by the microservice management platform, comprising:
the Redis acquires a preset micro-service subscription list;
for any micro service managed and controlled by the micro service management platform, the Redis judges whether the micro service exists in the micro service subscription list or not;
and if the micro service exists in the micro service subscription list, the Redis determines that the micro service is the target micro service.
3. The system of claim 1, wherein the target microservice obtaining the microservice configuration information and altering microservice configuration information local to the target microservice comprises:
and the target micro service acquires the micro service configuration information through a real-time timer configured by Spring Boot, and changes the local micro service configuration information of the target micro service.
4. The system of claim 1, wherein the target microservice obtaining the microservice configuration information and altering microservice configuration information local to the target microservice comprises:
the target micro service acquires the micro service configuration information;
the target micro service judges whether the micro service configuration information is suitable for the target micro service;
and if the micro-service configuration information is suitable for the target micro-service, the target micro-service utilizes the micro-service configuration information to change the local micro-service configuration information of the target micro-service.
5. The system of claim 4, wherein the target microservice determining whether the microservice configuration information applies to itself comprises:
the target micro service analyzes a micro service identifier carried in the micro service configuration information;
the target micro service judges whether the micro service identification is consistent with the self identification;
if the microservice configuration information is suitable for the microservice, the target microservice changes the microservice configuration information local to the target microservice by using the microservice configuration information, and the change comprises the following steps:
and if the micro-service identifier is consistent with the self identifier, the target micro-service utilizes the micro-service configuration information to change the local micro-service configuration information of the target micro-service.
6. The system of claim 5, further comprising:
and if the micro-service identifier is not consistent with the self identifier, the target micro-service deletes the micro-service configuration information.
7. The system of claim 4, wherein the target microservice determining whether the microservice configuration information applies to itself comprises:
extracting micro-service configuration original information in the micro-service configuration information by the target micro-service;
the target micro service judges whether the micro service configuration original information is consistent with the micro service configuration information of the target micro service;
if the microservice configuration information is suitable for the microservice, the target microservice changes the microservice configuration information local to the target microservice by using the microservice configuration information, and the change comprises the following steps:
and if the original micro-service configuration information is consistent with the local micro-service configuration information of the target micro-service, the target micro-service utilizes the micro-service configuration information to change the local micro-service configuration information of the target micro-service.
8. The system of claim 1, further comprising:
and if the original micro-service configuration information is not consistent with the local micro-service configuration information of the target micro-service, the target micro-service deletes the micro-service configuration information.
9. A method for managing micro service configuration information is applied to an API gateway, and comprises the following steps:
receiving micro service configuration information issued by a micro service management platform;
storing the micro-service configuration information to Redis, so that the Redis determines a target micro-service from a plurality of micro-services managed and controlled by the micro-service management platform, and pushes a notification of micro-service configuration information change to the target micro-service;
the notification of the change of the microservice configuration information is used for enabling the target microservice to acquire the microservice configuration information and change the microservice configuration information local to the target microservice.
10. A server is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing the communication between the processor and the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps as claimed in claim 9 when executing a program stored in the memory.
11. A storage medium on which a computer program is stored which, when being executed by a processor, carries out the method as claimed in claim 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010274081.XA CN111541561A (en) | 2020-04-09 | 2020-04-09 | Microservice configuration information management system, microservice configuration information management method, microservice configuration information management server, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010274081.XA CN111541561A (en) | 2020-04-09 | 2020-04-09 | Microservice configuration information management system, microservice configuration information management method, microservice configuration information management server, and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111541561A true CN111541561A (en) | 2020-08-14 |
Family
ID=71977058
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010274081.XA Pending CN111541561A (en) | 2020-04-09 | 2020-04-09 | Microservice configuration information management system, microservice configuration information management method, microservice configuration information management server, and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111541561A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112882738A (en) * | 2021-03-22 | 2021-06-01 | 亿企赢网络科技有限公司 | Configuration information updating method and device under micro-service architecture and electronic equipment |
| CN113765701A (en) * | 2021-08-02 | 2021-12-07 | 中企云链（北京）金融信息服务有限公司 | Gateway control method based on permanent memory cache |
| CN113765695A (en) * | 2021-03-26 | 2021-12-07 | 北京京东拓先科技有限公司 | Gateway management method, device, equipment and computer readable storage medium |
| CN114518909A (en) * | 2022-02-17 | 2022-05-20 | 中国建设银行股份有限公司 | Authorization information configuration method, device, equipment and storage medium based on API gateway |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105490843A (en) * | 2015-12-01 | 2016-04-13 | 努比亚技术有限公司 | Information processing method and system |
| CN106060138A (en) * | 2016-06-06 | 2016-10-26 | 北京小米移动软件有限公司 | Method and apparatus for updating data |
| CN107872525A (en) * | 2017-11-09 | 2018-04-03 | 杭州东方通信软件技术有限公司 | A kind of micro services call framework |
| CN108512748A (en) * | 2018-03-21 | 2018-09-07 | 上海艾融软件股份有限公司 | A kind of implementation method of micro services gateway |
| CN109656698A (en) * | 2018-12-14 | 2019-04-19 | 平安城市建设科技(深圳)有限公司 | Task processing method, management platform, actuating station and computer readable storage medium |
| CN110493067A (en) * | 2019-09-05 | 2019-11-22 | 中国银联股份有限公司 | A kind of method and device that API gateway service updates |
| CN110661662A (en) * | 2019-09-26 | 2020-01-07 | 北京北信源软件股份有限公司 | Lightweight microservice configuration method |
| CN110677475A (en) * | 2019-09-26 | 2020-01-10 | 亿企赢网络科技有限公司 | Micro-service processing method, device, equipment and storage medium |
-
2020
- 2020-04-09 CN CN202010274081.XA patent/CN111541561A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105490843A (en) * | 2015-12-01 | 2016-04-13 | 努比亚技术有限公司 | Information processing method and system |
| CN106060138A (en) * | 2016-06-06 | 2016-10-26 | 北京小米移动软件有限公司 | Method and apparatus for updating data |
| CN107872525A (en) * | 2017-11-09 | 2018-04-03 | 杭州东方通信软件技术有限公司 | A kind of micro services call framework |
| CN108512748A (en) * | 2018-03-21 | 2018-09-07 | 上海艾融软件股份有限公司 | A kind of implementation method of micro services gateway |
| CN109656698A (en) * | 2018-12-14 | 2019-04-19 | 平安城市建设科技(深圳)有限公司 | Task processing method, management platform, actuating station and computer readable storage medium |
| CN110493067A (en) * | 2019-09-05 | 2019-11-22 | 中国银联股份有限公司 | A kind of method and device that API gateway service updates |
| CN110661662A (en) * | 2019-09-26 | 2020-01-07 | 北京北信源软件股份有限公司 | Lightweight microservice configuration method |
| CN110677475A (en) * | 2019-09-26 | 2020-01-10 | 亿企赢网络科技有限公司 | Micro-service processing method, device, equipment and storage medium |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112882738A (en) * | 2021-03-22 | 2021-06-01 | 亿企赢网络科技有限公司 | Configuration information updating method and device under micro-service architecture and electronic equipment |
| CN113765695A (en) * | 2021-03-26 | 2021-12-07 | 北京京东拓先科技有限公司 | Gateway management method, device, equipment and computer readable storage medium |
| CN113765701A (en) * | 2021-08-02 | 2021-12-07 | 中企云链（北京）金融信息服务有限公司 | Gateway control method based on permanent memory cache |
| CN113765701B (en) * | 2021-08-02 | 2024-02-20 | 中企云链（北京）金融信息服务有限公司 | Gateway control method based on permanent memory cache |
| CN114518909A (en) * | 2022-02-17 | 2022-05-20 | 中国建设银行股份有限公司 | Authorization information configuration method, device, equipment and storage medium based on API gateway |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111541561A (en) | Microservice configuration information management system, microservice configuration information management method, microservice configuration information management server, and storage medium | |
| CN109213604B (en) | Data source management method and device | |
| CN109450969B (en) | Method and device for acquiring data from third-party data source server and server | |
| US9591059B2 (en) | File change notifications in a scale-out NAS system | |
| US20190278691A1 (en) | Automated recovery of flighted features based on service requests | |
| US11775358B2 (en) | Tenant copy operation in a microservice architecture | |
| CN111125240B (en) | Distributed transaction realization method and device, electronic equipment and storage medium | |
| US9826092B2 (en) | Method and system for call queue messaging | |
| CN104317660B (en) | A kind of bank's parameter management system | |
| CN110674153B (en) | Data consistency detection method and device and electronic equipment | |
| CN114693358A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN110083509B (en) | Method and device for arranging log data | |
| US11243968B2 (en) | Dynamic data service engine/router for content service management | |
| CN114090268A (en) | Container management method and container management system | |
| CN108399223B (en) | Data acquisition method and device and electronic equipment | |
| CN113778780A (en) | Application stability determination method and device, electronic equipment and storage medium | |
| CN111291127A (en) | Data synchronization method, device, server and storage medium | |
| CN113010587A (en) | Data source configuration method, device, terminal, server and medium | |
| CN113362097B (en) | User determination method and device | |
| CN116450622B (en) | Method, apparatus, device and computer readable medium for data warehouse entry | |
| CN111125223B (en) | Database connection pool updating method and device | |
| CN114285743B (en) | Method, device, electronic equipment and storage medium for updating configuration information | |
| CN113656772B (en) | Information processing method, information processing device, electronic equipment and storage medium | |
| CN110858848B (en) | Correction method and device for task resources of cluster system | |
| CN116578572A (en) | Service date changing method, device, equipment, storage medium and program product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200814 |
|
| RJ01 | Rejection of invention patent application after publication |