CN115857960A - Micro-service management system, method, device, storage medium and electronic equipment - Google Patents
Micro-service management system, method, device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN115857960A CN115857960A CN202211649528.2A CN202211649528A CN115857960A CN 115857960 A CN115857960 A CN 115857960A CN 202211649528 A CN202211649528 A CN 202211649528A CN 115857960 A CN115857960 A CN 115857960A
- Authority
- CN
- China
- Prior art keywords
- service
- component
- shared
- data
- management
- 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
Abstract
The invention discloses a micro-service management system, a micro-service management method, a micro-service management device, a storage medium and electronic equipment. Wherein, this system includes: the service management module is used for managing the functional components contained in the service functional module, wherein the functional components at least comprise business components and shared business components; the data sharing module is used for receiving first shared data sent by the service assembly and second shared data sent by the shared service assembly, and generating first release information and second release information based on the first shared data and the second shared data; the data storage module comprises at least one public component and is used for storing public data of the service components and the shared service components through the at least one public component; and the service function module is used for responding to the management instruction sent by the service management module and executing target operation based on the management instruction. The invention solves the technical problem that the micro-service management system in the prior art has poor flexibility in deploying micro-services.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a micro-service management system, a method, a device, a storage medium and electronic equipment.
Background
With the development of the digital society, the data traffic is larger and larger, a large number of enterprises transform the old services of the enterprises into the advanced clouding, and the enterprises are provided with services in a micro-service mode so as to improve the competitiveness of the enterprises.
At present, in the related art, a way of virtualizing the service as a whole is adopted to implement service clouding, that is, the service runs in a cloud platform in a virtual server manner and is managed by a micro-service management system. However, services are operated in a whole manner, service components are tightly coupled, and as long as one component has a problem, the whole service flow may be blocked and the service cannot be normally provided. Moreover, with the rapid increase of the service volume, an enterprise may have hundreds of services online, and the service cloud is realized by adopting the above manner, for the services, all the services are completely developed independently, no cooperation or communication exists between the services, and the interior of the service is relatively black, so that a large amount of repeated work exists in the service design and development process, for example, how to select and configure a relevant database, and the like. In many cases, the databases and architectures of different services selected in the design and development process are completely the same, so that two different groups of people maintain the same functional component, and the problem of human resource waste exists. In addition, after a certain service is upgraded, all other services using the service need to be developed and changed correspondingly, that is, other services need to interact with the service, and the problem of low efficiency of information and data interaction between services exists.
In addition, because the service runs in an integral mode, the service components are tightly coupled, the service functions and the data are bound in the same service instance, when the expansion requirement for a certain function of the service exists, the service can only be expanded integrally, the problems of unbalanced resource distribution, inadaptability to manage and the like exist, and the flexible deployment of the micro-service cannot be realized.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the invention provides a micro-service management system, a micro-service management method, a micro-service management device, a storage medium and electronic equipment, and at least solves the technical problem that the micro-service management system in the prior art is poor in micro-service deployment flexibility.
According to an aspect of an embodiment of the present invention, there is provided a micro service management system including: the service management module is used for managing the functional components contained in the service functional module, wherein the functional components at least comprise business components and shared business components; the data sharing module is used for receiving first shared data sent by the service component and second shared data sent by the shared service component, and generating first publishing information and second publishing information based on the first shared data and the second shared data, wherein the first publishing information and the second publishing information are used for prompting a target component to pay attention to the first shared data and the second shared data, and the target component is a component for monitoring the first shared data and the second shared data in the service component and the shared service component; the data storage module comprises at least one public component and is used for storing public data of the service component and the shared service component through the at least one public component; the service function module is used for responding to the management instruction sent by the service management module and executing target operation based on the management instruction, wherein the management instruction comprises at least one of the following: the method comprises the following steps of expanding instructions and backing up instructions, wherein target operation comprises at least one of the following steps: expansion operation and backup operation.
Further, the service function module is further configured to obtain device information of the target device through the service component and the shared service component, and send the device information to the data sharing module, where the target device is a device managed by the service component and the shared service component.
Further, the service function module is further configured to send the interface information of the service component and the shared service component to the data sharing module, so that the service management module obtains the device information and the interface information from the data sharing module, and manages the target device based on the interface information.
According to an aspect of an embodiment of the present invention, there is provided a micro service management method, including: generating at least one business component in response to the first management instruction; acquiring interface information of at least one service component and sending the interface information to a data sharing module; and responding to the second management instruction, acquiring the interface information from the data sharing module, and managing the target equipment based on the interface information.
Further, the micro-service management method further comprises: after responding to the first management instruction and generating at least one service component, responding to a connection request sent by target equipment, and connecting the at least one service component with the target equipment; and under the condition that the at least one service component is in a connection state with the target equipment, acquiring equipment information of the target equipment through the at least one service component, and sending the equipment information to the data sharing module.
Further, the micro-service management method further comprises: responding to the second management instruction, and acquiring interface information and equipment information from the data sharing module; and managing the target equipment based on the interface information and the equipment information.
According to another aspect of the embodiments of the present invention, there is also provided a micro service management apparatus, including: the first processing module is used for responding to the first management instruction and generating at least one business component; the acquisition module is used for acquiring interface information of at least one service component and sending the interface information to the data sharing module; and the second processing module is used for responding to the second management instruction, acquiring the interface information from the data sharing module and managing the target equipment based on the interface information.
According to another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned micro-service management method when running.
According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including one or more processors; a memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a method for running a program, wherein the program is arranged to perform the above-described microservice management method when running.
According to another aspect of the embodiments of the present invention, there is also provided a computer program product, which includes a computer program/instruction, and the computer program/instruction, when executed by a processor, implements the micro-service management method described above.
In the embodiment of the invention, the mode of service hierarchical design is adopted to realize the complete decoupling of each component in the service, namely, each component can be independently deployed, expanded and backed up with data. The service management module can manage the functional components contained in the service function module, and after a certain service function is expanded into multiple instances, the single service management module can realize the management of the multiple instances of the service function and more conveniently manage the multiple service instances; through the data sharing module, data sharing among services is realized, and the data interaction efficiency is improved; through the service function module, independent expansion and backup of a certain service function can be realized, and the utilization rate of service resources is improved; through the public component in the data storage module, the public data of the service component and the shared service component can be stored, the function component which is used by most services is independent and can be directly used by designers as the public function component, independent type selection, development and maintenance are not needed, the repeated workload of maintenance and development is reduced, the labor cost and the time cost are saved, and the development efficiency is improved.
Therefore, through the technical scheme of the invention, the purposes that each component in the service can be independently deployed, expanded and backed up by data and all the components are completely decoupled through the service hierarchical design are achieved, so that the technical effect of improving the flexibility of deploying the micro-service is realized, and the technical problem that the micro-service management system in the prior art is poor in flexibility of deploying the micro-service is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a schematic diagram of an alternative microservice management system in accordance with embodiments of the present invention;
FIG. 2 is a flow chart of an alternative method of micro-service management according to an embodiment of the present invention;
FIG. 3 is an architecture diagram of an alternative microservice management system in accordance with an embodiment of the present invention;
FIG. 4 is an architecture diagram of an alternative dynamic extension and backup of service components in accordance with an embodiment of the present invention;
FIG. 5 is a schematic diagram of an application of an alternative microservice management system in accordance with an embodiment of the present invention;
fig. 6 is a schematic diagram of an alternative microservice management apparatus according to an embodiment of the invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, 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 only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be noted that the related information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for presentation, analyzed data, etc.) related to the present invention are information and data authorized by the user or sufficiently authorized by each party. For example, an interface is provided between the system and the relevant user or institution, and before obtaining the relevant information, an obtaining request needs to be sent to the user or institution through the interface, and after receiving the consent information fed back by the user or institution, the relevant information needs to be obtained.
Example 1
In accordance with an embodiment of the present invention, there is provided a method embodiment of a microservice management method, it being noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than presented herein.
Fig. 1 is a schematic diagram of an alternative microservice management system according to an embodiment of the present invention, as shown in fig. 1, the system comprising: the service management module is used for managing the functional components contained in the service functional module, wherein the functional components at least comprise business components and shared business components; the data sharing module is used for receiving first shared data sent by the service component and second shared data sent by the shared service component, and generating first publishing information and second publishing information based on the first shared data and the second shared data, wherein the first publishing information and the second publishing information are used for prompting a target component to pay attention to the first shared data and the second shared data, and the target component is a component for monitoring the first shared data and the second shared data in the service component and the shared service component; the data storage module comprises at least one public component and is used for storing public data of the service components and the shared service components through the at least one public component; the service function module is used for responding to the management instruction sent by the service management module and executing target operation based on the management instruction, wherein the management instruction comprises at least one of the following: the method comprises the following steps of expanding instructions and backing up instructions, wherein target operation comprises at least one of the following steps: expansion operation and backup operation.
Optionally, fig. 3 is an architecture diagram of an alternative micro-service management system according to an embodiment of the present invention, and as shown in fig. 3, the micro-service management system includes a service management component, a shared object repository, a service function shared database, and a service function component. Optionally, the service management module may be a service management component, the data sharing module may be a shared object repository, the data storage module may be a service function shared database, and the service function module may be a service function component.
The service management module, i.e., the service management component, includes a common/shared service management component (e.g., shared service management component, shared resource management component), a business management component (e.g., service a management component, service B management component, service C management component). The Data storage module, i.e., the service function shared database, includes a plurality of common components, for example, a log shared Database (DB) function component, a configuration shared DB function component, a statistics shared DB function component, a Data lake function component. Service function modules, i.e., service function components, include common/shared business components (e.g., shared service a, shared service B), business components (e.g., service a, service B, service C).
Optionally, in this embodiment, the service is no longer a bound whole, but the internal structure of the service is divided into three layers: service management, service function sharing database, service function, and adding sharing object warehouse layer to realize decoupling between service components. Optionally, the components in each layer may be independently deployed on different nodes, each component may be independently developed by using different programming languages and different deployment manners (e.g., container deployment, virtual server deployment, physical server deployment, etc.), and the components in each layer may perform information or data interaction through a Representational State Transfer (REST) API interface.
Optionally, in this embodiment, a shared object warehouse component, that is, a data sharing module, is introduced, so that data sharing among the services is realized. For example, the service component a sends first shared data, the shared service component B sends second shared data to a shared object repository, generates first publishing information and second publishing information in a Publish/Subscribe (Publish/Subscribe) interactive manner, and prompts a target component (e.g., a service component C monitoring the first shared data and the second shared data) to pay attention to the first shared data and the second shared data. Specifically, the service may monitor the data object concerned, and after the monitored object performs operations such as adding, modifying, deleting data, and the like, each service receives the notification, thereby implementing efficient interaction of data.
It should be noted that, data sharing is realized through the shared object warehouse, and the problem of low efficiency caused by interaction among services in the related art is solved.
Optionally, in this embodiment, a common component that most services will use together is separated to serve as a service function shared database, which can be independently developed, deployed and maintained. For example, most services use database functions, statistical functions, logging functions, data analysis functions, message caching functions, and the like. Taking the function of the database as an example, based on different service requirements, the used databases are different in type, different databases have different performance tuning methods, different cluster (cluster) deployment and data backup modes, shared database software is provided for each service team through a common component, each service team only needs to independently develop, deploy and maintain a functional component strongly related to own service based on the common component, and mutual access is realized through a universal REST API (reduced instruction set interface).
Optionally, in this embodiment, because each component in the service can be independently deployed, independently extended, and independently backed up, when any one of the sub-components fails, the overall service is not affected, so that the lateral extension is better achieved, various requirements of a user can be met, better service is provided for the user, and user experience is improved. For example, only one service management component is needed, but three functional components of the service, namely the service body, are needed, only one database is needed, and the data backup can be realized through independent deployment, independent extension and independent data backup of each component.
Optionally, in this embodiment, the service body may be redundantly backed up through the service component, and specifically, the redundancy backup may be performed based on Load Balance (Load Balance) of the service. In this case, the service itself will not make data backup, the service function of multiple instances distributes service requests through load balancing of components, when one instance is hung (down), the user re-initiates the request, and the new request will be distributed to the instance in running (up) state for execution. For example, after the service functional components are backed up, there are 2 functional components, and when one of the functional components is hung, the user request is distributed to the functional components which are not hung for running continuously next time.
Optionally, when there is a need to backup data of the service itself, the service body may be redundantly backed up through the service component. For example, for a specific service with a strong requirement on the coherence of service requests, the service itself supports dynamic backup of data, and needs to deploy a corresponding High Availability (HA) redundant backup instance for the service, and mutually backs up the service and the data for the peer node.
Optionally, fig. 4 is an architecture diagram of optional dynamic extension and backup of a service component according to an embodiment of the present invention, as shown in fig. 4, an extended service function is a multi-instance, that is, a service a is extended into a service a-1, a service a-2, a service a-3, a service a-4, a service a-5, and a service a-6 through a service component, and a corresponding high-availability instance is redundantly backed up: A-1-HA, A-2-HA, A-3-HA, A-4-HA, A-5-HA, A-6-HA.
Furthermore, the management of the single service management component on the multiple instances of the service function is realized through the shared object warehouse. Specifically, as shown in fig. 4, the above 6 instances may be managed by a service a-1 management component in the service management component. Wherein, the service A-2 management component can be a management component expanded based on the service A-1 management component.
Optionally, all the service function instances share the data that can be managed, operated, and displayed in the shared object repository, and a single service management component can see the objects that are serviced and managed by all the expanded service function instances, and can operate the objects that are serviced and managed by each instance, thereby achieving effective expansion of the service function instances.
Specifically, the service function module is further configured to obtain device information of the target device through the service component and the shared service component, and send the device information to the data sharing module, where the target device is a device managed by the service component and the shared service component.
Optionally, the target device may be a service component and a device managed by a shared service component, and the device information may be device ID and other information.
Optionally, in this embodiment, efficient data sharing is implemented between the service components in a star interaction manner of the shared object repository. Specifically, the shared data of the service is published to the shared object repository, and all other services concerned about this data can listen to the data.
The shared object repository can provide the operation mode of Full REST API and the data interaction mechanism of Publish/Subscribe. Secure link Access and Role Based Access Control (RBAC) may also be provided. The shared object warehouse also supports a mechanism of data synchronization and active acquisition, supports the characteristics of expandability and redundancy backup of data storage, and supports the control of data storage versions.
Specifically, the service function module is further configured to send interface information of the service component and the shared service component to the data sharing module, so that the service management module obtains the device information and the interface information from the data sharing module, and manages the target device based on the interface information. Alternatively, the interface information may be management interface information for managing instances of service function components, e.g., API interface information for service components and shared service components to provide service interaction.
The present invention is described below with reference to preferred implementation steps, and fig. 2 is a flowchart of an alternative micro service management method according to an embodiment of the present invention, as shown in fig. 2, the method includes the following steps:
step S201, responding to a first management instruction, and generating at least one business component;
step S202, acquiring interface information of at least one service component, and sending the interface information to a data sharing module;
step S203, responding to the second management instruction, acquiring the interface information from the data sharing module, and managing the target device based on the interface information.
In the above step, the first management instruction may be an extension instruction, and specifically, the extension is a horizontal extension of the service function instance. And generating at least one business component, such as service A, service B and service C, by the service functional component in response to the extended instruction. The second management instruction may be an information obtaining instruction, and interface information, i.e., API interface information for providing service interaction for service a, service B, and service C, may be obtained from the data sharing module, i.e., the shared object repository, in response to the information obtaining instruction through the service management component, so that devices managed by service a, service B, and service C, respectively, may be managed through the API interface information.
In the embodiment of the invention, the mode of service hierarchical design is adopted to realize the complete decoupling of each component in the service, namely, each component can be independently deployed, expanded and backed up with data. The service management module can manage the functional components contained in the service function module, and after a certain service function is expanded into multiple instances, the single service management module can realize the management of the multiple instances of the service function and more conveniently manage the multiple service instances; through the data sharing module, data sharing among services is realized, and the data interaction efficiency is improved; through the service function module, independent expansion and backup of a certain service function can be realized, and the utilization rate of service resources is improved; the common component in the data storage module can store the common data of the service component and the shared service component, so that the independent deployment and maintenance of the functional components used by most services are realized, the common component is directly used by other micro-services, independent type selection, development and maintenance are not needed, the repeated workload of maintenance and development is reduced, the labor cost and the time cost are saved, and the development efficiency is improved.
Therefore, through the technical scheme of the invention, the purposes that each component in the service can be independently deployed, expanded and backed up by data and all the components are completely decoupled through the service hierarchical design are achieved, so that the technical effect of improving the flexibility of deploying the micro-service is realized, and the technical problem that the micro-service management system in the prior art is poor in flexibility of deploying the micro-service is solved.
In an optional embodiment, after the at least one service component is generated in response to the first management instruction, the at least one service component is connected with the target device in response to a connection request sent by the target device; and under the condition that the at least one service component is in a connection state with the target equipment, acquiring equipment information of the target equipment through the at least one service component, and sending the equipment information to the data sharing module.
In an optional embodiment, in the process of responding to the second management instruction, acquiring the interface information from the data sharing module, and managing the target device based on the interface information, first responding to the second management instruction, acquiring the interface information and the device information from the data sharing module, and then managing the target device based on the interface information and the device information.
Optionally, fig. 5 is an application schematic diagram of an optional micro service management system according to an embodiment of the present invention, and as shown in fig. 5, a Point-of-Presence (PoP) device is managed by the micro service management system, specifically, first, three PoP Point service instances are horizontally started in a service function component by a shared service management component: the service function component responds to a first management instruction sent by the shared service management component to generate at least one service component. The service function body can be configuration management and equipment management.
Further, as shown in fig. 5, each PoP point service instance registers an API that provides service interaction with itself into the shared object repository, that is, obtains interface information of at least one service component, and sends the interface information to the data sharing module.
Further, as shown in fig. 5, all devices in the resource layer are connected to their corresponding PoP point service instances, that is, the devices are connected to PoP point service a, poP point service B, and PoP point service C, that is, in response to a connection request sent by a target device, at least one service component is connected to the target device. Wherein each PoP point service instance can manage up to 3000 devices.
Further, under the condition that at least one service component is in a connection state with the target device, the PoP point service a, the PoP point service B, and the PoP point service C synchronously share all registered device information to the shared object repository, that is, the device information of the target device is acquired through at least one service component, and the device information is sent to the data sharing module.
Further, as shown in fig. 5, the PoP point management component may obtain the device information and the interface information registered in all instances of the "PoP point service" from the shared object repository, that is, in response to the second management instruction, obtain the interface information and the device information from the data sharing module.
Further, as shown in fig. 5, the PoP point management component may see at most 9000 devices, know to which "PoP point service" instance each device belongs, and may manage through the service API interface corresponding to the instance, that is, manage the target device based on the interface information and the device information.
It should be noted that, in the above process, after service clouding is realized by deployment, a guarantee is provided for interaction between services, and business elasticity in the big data era is better adapted. For the components which can be shared among the services, the development, operation and maintenance costs are reduced by realizing the sharing; the service and the data are completely separated, the service and the data can be independently expanded and redundantly backed up instead of the service as a whole, the problems that the data and the service are bound, the service expansion granularity is too large and the management and the service cannot be separated in the related technology are solved, the service management, the service function and the service data are separated, and the method gets rid of 1:1: the ratio of 1 can better allocate resources according to the actual service request quantity and the management requirement; a shared object warehouse component is introduced, so that data sharing among services is realized, and unique storage and integrity of data are guaranteed; by uniformly maintaining the common components, the development and maintenance of the components are reduced, and the service expansion is more flexible; each of the three instances can be independently expanded and maintained, for example, the database 'etcd' can be used for deploying the three instances as a cluster, the three instances simultaneously perform data redundancy backup mutually, the query efficiency can be improved, and all services using the 'etcd' do not need to deploy and maintain the 'etcd' independently.
Therefore, through the technical scheme of the invention, the purposes that each component in the service can be independently deployed, expanded and backed up by data and all the components are completely decoupled through the service hierarchical design are achieved, so that the technical effect of improving the flexibility of deploying the micro-service is realized, and the technical problem that the micro-service management system in the prior art is poor in flexibility of deploying the micro-service is solved.
Example 2
According to an embodiment of the present invention, an embodiment of a micro service management device is provided, where fig. 6 is a schematic diagram of an alternative micro service management device according to an embodiment of the present invention, as shown in fig. 6, the device includes: a first processing module 601, configured to generate at least one service component in response to a first management instruction; an obtaining module 602, configured to obtain interface information of at least one service component, and send the interface information to a data sharing module; the second processing module 603 is configured to, in response to the second management instruction, obtain interface information from the data sharing module, and manage the target device based on the interface information.
It should be noted that the first processing module 601, the obtaining module 602, and the second processing module 603 correspond to steps S201 to S203 in the foregoing embodiment, and the three modules are the same as the corresponding steps in implementation examples and application scenarios, but are not limited to the disclosure of embodiment 1.
Optionally, the micro service management apparatus further includes: the third processing module is used for responding to a connection request sent by the target equipment and connecting at least one service component with the target equipment; and the fourth processing module is used for acquiring the equipment information of the target equipment through the at least one service component and sending the equipment information to the data sharing module under the condition that the at least one service component is in a connection state with the target equipment.
Optionally, the second processing module includes: the acquisition unit is used for responding to the second management instruction and acquiring the interface information and the equipment information from the data sharing module; and the management unit is used for managing the target equipment based on the interface information and the equipment information.
Optionally, a micro service management system manages a device access point (PoP), specifically, first, a shared service management component horizontally starts three PoP point service instances in a service function component: the service function component responds to a first management instruction sent by the shared service management component to generate at least one service component. Wherein each PoP point service instance comprises a configuration management component and a device management component.
Furthermore, each PoP point service instance registers an API that provides service interaction with itself into the shared object repository, that is, obtains interface information of at least one service component, and sends the interface information to the data sharing module.
Further, all devices in the resource layer are connected to their corresponding PoP point service instances, that is, the devices are connected to PoP point service a, poP point service B, and PoP point service C, respectively, that is, in response to a connection request sent by the target device, at least one service component is connected to the target device. Wherein each PoP point service instance can manage up to 3000 devices.
Further, under the condition that at least one service component is in a connection state with the target device, the PoP point service a, the PoP point service B and the PoP point service C synchronously share all registered device information to a shared object warehouse, that is, the device information of the target device is acquired through at least one service component, and the device information is sent to the data sharing module.
Further, the PoP point management component may obtain the device information and the interface information registered in all the "PoP point service" instances from the shared object repository, that is, in response to the second management instruction, obtain the interface information and the device information from the data sharing module.
Further, the PoP point management component may see at most 9000 devices, know to which "PoP point service" instance each device belongs, and may manage through a service API interface corresponding to the instance, that is, manage the target device based on the interface information and the device information.
It should be noted that, in the above process, after service clouding is realized by deployment, a guarantee is provided for interaction between services, and business elasticity in the big data era is better adapted. For the components which can be shared among the services, the development, operation and maintenance costs are reduced by realizing the sharing; the service and the data are completely separated, the service and the data can be independently expanded and redundantly backed up instead of the service as a whole, the problems that the data and the service are bound, the service expansion granularity is too large and the management and the service cannot be separated in the related technology are solved, the service management, the service function and the service data are separated, and the method gets rid of 1:1: the ratio of 1 can better allocate resources according to the actual service request quantity and the management requirement; a shared object warehouse component is introduced, so that data sharing among services is realized, and unique storage and integrity of data are guaranteed; by uniformly maintaining the common components, the development and maintenance of the components are reduced, and the service expansion is more flexible; each of the three instances can be independently expanded and maintained, for example, the database 'etcd' can be used for deploying the three instances as a cluster, the three instances simultaneously perform data redundancy backup mutually, the query efficiency can be improved, and all services using the 'etcd' do not need to deploy and maintain the 'etcd' independently.
Example 3
According to another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned micro-service management method when running.
Example 4
According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including one or more processors; a memory for storing one or more programs that, when executed by the one or more processors, cause the one or more processors to implement a method for running the programs, wherein the programs are arranged to perform the above-described micro-service management method when run.
Example 5
According to another aspect of the embodiments of the present invention, there is also provided a computer program product, which includes a computer program/instruction, when executed by a processor, the computer program/instruction implements the above-mentioned micro service management method.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
In the above embodiments of the present invention, the description of each embodiment has its own emphasis, and reference may be made to the related description of other embodiments for parts that are not described in detail in a certain embodiment.
In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention, which is substantially or partly contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A microservice management system, comprising:
the service management module is used for managing the functional components contained in the service functional module, wherein the functional components at least comprise business components and shared business components;
a data sharing module, configured to receive first shared data sent by the service component and second shared data sent by the shared service component, and generate first publishing information and second publishing information based on the first shared data and the second shared data, where the first publishing information and the second publishing information are used to prompt a target component to pay attention to the first shared data and the second shared data, and the target component is a component that monitors the first shared data and the second shared data in the service component and the shared service component;
the data storage module comprises at least one public component and is used for storing public data of the business component and the shared business component through the at least one public component;
the service function module is configured to respond to a management instruction sent by the service management module and execute a target operation based on the management instruction, where the management instruction includes at least one of: the target operation comprises at least one of the following operations: expansion operation and backup operation.
2. The system according to claim 1, wherein the service function module is further configured to obtain device information of a target device through the service component and the shared service component, and send the device information to the data sharing module, where the target device is a device managed by the service component and the shared service component.
3. The system according to claim 2, wherein the service function module is further configured to send interface information of the service component and the shared service component to the data sharing module, so that the service management module obtains the device information and the interface information from the data sharing module, and manages the target device based on the interface information.
4. A microservice management method applied to the microservice management system according to any one of claims 1 to 3, comprising:
generating at least one business component in response to the first management instruction;
acquiring interface information of the at least one service component, and sending the interface information to a data sharing module;
and responding to a second management instruction, acquiring the interface information from the data sharing module, and managing the target equipment based on the interface information.
5. The method of claim 4, wherein after generating at least one business component in response to the first management instruction, the method further comprises:
responding to a connection request sent by the target equipment, and connecting the at least one service component with the target equipment;
and under the condition that the at least one service component is in a connection state with the target equipment, acquiring equipment information of the target equipment through the at least one service component, and sending the equipment information to the data sharing module.
6. The method of claim 5, wherein obtaining the interface information from the data sharing module in response to a second management instruction, and managing the target device based on the interface information comprises:
responding to a second management instruction, and acquiring the interface information and the equipment information from the data sharing module;
and managing the target equipment based on the interface information and the equipment information.
7. A microservice management apparatus, comprising:
the first processing module is used for responding to the first management instruction and generating at least one business component;
the acquisition module is used for acquiring the interface information of the at least one service component and sending the interface information to the data sharing module;
and the second processing module is used for responding to a second management instruction, acquiring the interface information from the data sharing module and managing the target equipment based on the interface information.
8. A computer-readable storage medium, in which a computer program is stored, wherein the computer program is arranged to execute the microservice management method of any of the claims 4 to 6 when running.
9. An electronic device, wherein the electronic device comprises one or more processors; memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a method for running a program, wherein the program is arranged to perform the microservice management method of any of claims 4 to 6 when run.
10. A computer program product comprising computer programs/instructions, characterized in that the computer programs/instructions, when executed by a processor, implement the microservice management method of any of claims 4 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211649528.2A CN115857960A (en) | 2022-12-21 | 2022-12-21 | Micro-service management system, method, device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211649528.2A CN115857960A (en) | 2022-12-21 | 2022-12-21 | Micro-service management system, method, device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115857960A true CN115857960A (en) | 2023-03-28 |
Family
ID=85674937
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211649528.2A Pending CN115857960A (en) | 2022-12-21 | 2022-12-21 | Micro-service management system, method, device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115857960A (en) |
-
2022
- 2022-12-21 CN CN202211649528.2A patent/CN115857960A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110737442B (en) | Edge application management method and system | |
| CN106776998B (en) | Database service providing method and server | |
| US9077613B2 (en) | System and method for graph based K-redundant resiliency for IT cloud | |
| CN106888245B (en) | Data processing method, device and system | |
| US11308223B2 (en) | Blockchain-based file handling | |
| US20120278817A1 (en) | Event distribution pattern for use with a distributed data grid | |
| CN105308553B (en) | Dynamic provides storage | |
| CN107818104B (en) | Database deployment method, database deployment device, control equipment and system | |
| Kanso et al. | Achieving high availability at the application level in the cloud | |
| KR101765725B1 (en) | System and Method for connecting dynamic device on mass broadcasting Big Data Parallel Distributed Processing | |
| CN112882738A (en) | Configuration information updating method and device under micro-service architecture and electronic equipment | |
| CN103797461B (en) | Network system | |
| CN112492022A (en) | Cluster, method, system and storage medium for improving database availability | |
| CN110753069B (en) | Method, device and storage medium for cloud desktop offline management | |
| CN114565502A (en) | GPU resource management method, scheduling method, device, electronic equipment and storage medium | |
| e Silva et al. | Application execution management on the InteGrade opportunistic grid middleware | |
| CN116112569B (en) | Micro-service scheduling method and management system | |
| CN114615268B (en) | Service network, monitoring node, container node and equipment based on Kubernetes cluster | |
| US10110502B1 (en) | Autonomous host deployment in managed deployment systems | |
| CN115857960A (en) | Micro-service management system, method, device, storage medium and electronic equipment | |
| US20150244780A1 (en) | System, method and computing apparatus to manage process in cloud infrastructure | |
| CN105262796A (en) | Cloud platform storage resource management system and disposition framework thereof | |
| US9612927B1 (en) | Managing server processes with proxy files | |
| CN115037757A (en) | Multi-cluster service management system | |
| CN111381921B (en) | Front-end and back-end separation system and method based on Ambari |
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 |