Microservice Management System, Method, Device, Storage Medium and Electronic Device

Abstract

The present invention discloses a microservice management system, method, device, storage medium and electronic device. Among them, the system includes: a service management module for managing the functional components included in the service function module, where the functional components at least include business components and shared business components; a data sharing module for receiving first shared data sent by the business components and second shared data sent by the shared business components, and generating first release information and second release information based on the first shared data and the second shared data; a data storage module including at least one common component for storing the common data of the business components and the shared business components through the at least one common component; a service function module for responding to the management instruction sent by the service management module and performing a target operation based on the management instruction. The present invention solves the technical problem that the microservice management system in the prior art has poor flexibility in deploying microservices.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular, to a microservice management system, method, device, storage medium, and electronic device. Background Art

[0002] With the development of the digital society, the data traffic is increasing. A large number of enterprises upgrade and cloudify their old services, and provide services to users in the form of microservices to enhance their competitiveness.

[0003] Currently, in the related art, the overall virtualization of services is adopted to realize service cloudification, that is, the service runs in the cloud platform in the form of a virtual server and is managed by a microservice management system. However, the service runs as a whole, and the service components are tightly coupled. As long as one component has a problem, the entire service flow may be blocked and the service cannot be provided normally. Moreover, with the sharp increase in the service volume, hundreds or thousands of services will be launched by enterprises. Using the above method to realize service cloudification, for services, all services are developed completely independently, there is no cooperation or communication between services, and the service is relatively black box inside, resulting in a large amount of repetitive work in the service design and development process. For example, how to select and configure relevant databases, etc. In many cases, the databases and architectures selected in the design and development processes of different services are exactly the same, resulting in the same functional components being maintained by two different groups of people, wasting human resources. In addition, when a certain service is upgraded, all other services that use this service need to make corresponding development changes, that is, all other services need to interact with this service, resulting in low efficiency of information and data interaction between services.

[0004] In addition, since the service runs as a whole and the service components are tightly coupled, the service function and data are bound in the same service instance. When there is a need to expand a certain function of the service, only the whole service can be expanded, resulting in problems such as unbalanced resource allocation and inconvenient management, and it is impossible to achieve flexible deployment of microservices.

[0005] In view of the above problems, no effective solution has been proposed yet. Summary of the Invention

[0006] Embodiments of the present invention provide a microservice management system, method, device, storage medium, and electronic device, so as to at least solve the technical problem of poor flexibility in deploying microservices in the existing microservice management system.

[0007] According to one aspect of an embodiment of the present invention, a microservice management system is provided, including: a service management module for managing functional components included in a service function module, where the functional components at least include business components and shared business components; a data sharing module for receiving first shared data sent by a business component and second shared data sent by a shared business component, and generating first release information and second release information based on the first shared data and the second shared data, where the first release information and the second release 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 listens to the first shared data and the second shared data among the business components and the shared business components; a data storage module including at least one common component for storing common data of the business components and the shared business components through the at least one common component; a service function module for responding to a management instruction sent by the service management module and performing a target operation based on the management instruction, where the management instruction includes at least one of the following: an expansion instruction, a backup instruction, and the target operation includes at least one of the following: an expansion operation, a backup operation.

[0008] Further, the service function module is further configured to obtain device information of a target device through the business components and the shared business components, and send the device information to the data sharing module, where the target device is a device managed by the business components and the shared business components.

[0009] Further, the service function module is further configured to send interface information of the business components and the shared business components 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.

[0010] According to one aspect of an embodiment of the present invention, a microservice management method is provided, including: responding to a first management instruction to generate at least one business component; obtaining interface information of the at least one business component, and sending the interface information to the data sharing module; responding to a second management instruction to obtain the interface information from the data sharing module, and managing a target device based on the interface information.

[0011] Further, the microservice management method further includes: after responding to the first management instruction to generate at least one business component, responding to a connection request sent by the target device to connect the at least one business component to the target device; when the at least one business component and the target device are in a connected state, obtaining device information of the target device through the at least one business component, and sending the device information to the data sharing module.

[0012] Further, the microservice management method further includes: responding to the second management instruction to obtain the interface information and the device information from the data sharing module; managing the target device based on the interface information and the device information.

[0013] According to another aspect of the embodiments of the present invention, there is also provided a microservice management device, including: a first processing module, configured to generate at least one service component in response to a first management instruction; an acquisition module, configured to acquire interface information of at least one service component and send the interface information to a data sharing module; a second processing module, configured to acquire the interface information from the data sharing module in response to a second management instruction and manage a target device based on the interface information.

[0014] According to another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the above-mentioned microservice management method when running.

[0015] 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, configured to store one or more programs, and when the one or more programs are executed by the one or more processors, enable the one or more processors to implement running the program, wherein the program is configured to execute the above-mentioned microservice management method when running.

[0016] According to another aspect of the embodiments of the present invention, there is also provided a computer program product, including a computer program / instructions, and when the computer program / instructions are executed by a processor, the above-mentioned microservice management method is implemented.

[0017] In the embodiments of the present invention, by adopting a service layering design method, complete decoupling of each component inside the service is achieved, that is, each component can be independently deployed, extended, and data-backed up. Through the service management module, the functional components included in the service function module can be managed. After a certain service function is extended to multiple instances, through a single service management module, management of multiple instances of the service function can be realized, and it is more convenient to manage multiple service instances; through the data sharing module, data sharing between services is realized, improving the efficiency of data interaction; through the service function module, separate extension and backup of a certain service function can be realized, improving the utilization rate of service resources; through the common components in the data storage module, the common data of service components and shared service components can be stored, realizing the separation of functional components that most services will use as common functional components for designers to directly use, without the need for separate selection, development, and maintenance, reducing the repetitive workload of maintenance and development, saving labor costs and time costs, and improving development efficiency.

[0018] It can be seen that through the technical solution of the present invention, the purpose of enabling each component within the service to be independently deployed, extended, and data-backed up, and completely decoupling each component, is achieved through service layer design, thereby achieving the technical effect of improving the flexibility of deploying microservices, and further solving the technical problem of poor flexibility in deploying microservices in the existing microservice management system. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present invention, and constitute a part of this application. The illustrative embodiments of the present invention and their descriptions are used to explain the present invention, and do not constitute an improper limitation of the present invention. In the drawings:

[0020] Figure 1 is a schematic diagram of an optional microservice management system according to an embodiment of the present invention;

[0021] Figure 2 is a flowchart of an optional microservice management method according to an embodiment of the present invention;

[0022] Figure 3 is an architecture diagram of an optional microservice management system according to an embodiment of the present invention;

[0023] Figure 4 is an architecture diagram of an optional dynamic expansion and backup of service components according to an embodiment of the present invention;

[0024] Figure 5 is an application schematic diagram of an optional microservice management system according to an embodiment of the present invention;

[0025] Figure 6 is a schematic diagram of an optional microservice management device according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0026] In order to enable those skilled in the art to better understand the solution of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0027] It should be noted that the terms "first", "second", etc. in the description, claims and above-mentioned drawings of the present invention are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present invention described here can be implemented in an order other than those illustrated or described here. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0028] It should be noted that the relevant information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in the present invention are all information and data authorized by the user or fully authorized by all parties. For example, an interface is set between the present system and relevant users or institutions. Before obtaining relevant information, a request for acquisition needs to be sent to the aforementioned users or institutions through the interface, and after receiving the consent information feedback from the aforementioned users or institutions, the relevant information is obtained.

[0029] Embodiment 1

[0030] According to an embodiment of the present invention, a method embodiment of a microservice management method is provided. It should be noted that the steps shown in the flowchart of the drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described here can be executed in a different order than here.

[0031] Figure 1 is a schematic diagram of an optional microservice management system according to an embodiment of the present invention, as Figure 1As shown in the figure, the system includes: a service management module for managing the functional components included in the service function module, where the functional components at least include business components and shared business components; a data sharing module for receiving the first shared data sent by the business components and the second shared data sent by the shared business components, and generating first release information and second release information based on the first shared data and the second shared data, where the first release information and the second release information are used to prompt the target components to pay attention to the first shared data and the second shared data, and the target components are the components in the business components and the shared business components that listen to the first shared data and the second shared data; a data storage module including at least one common component for storing the common data of the business components and the shared business components through the at least one common component; a service function module for responding to the management instructions sent by the service management module and performing target operations based on the management instructions, where the management instructions include at least one of the following: an expansion instruction and a backup instruction, and the target operations include at least one of the following: an expansion operation and a backup operation.

[0032] Optionally, Figure 3 is an architecture diagram of an optional microservice management system according to an embodiment of the present invention, as Figure 3 shown, the microservice management system includes a service management component, a shared object repository, a service function shared database, and service function components. Optionally, the service management module may be the service management component, the data sharing module may be the shared object repository, the data storage module may be the service function shared database, and the service function module may be the service function components.

[0033] Among them, the service management module, that is, the service management component, includes a public / shared service management component (for example, a shared service management component, a shared resource management component), and a business management component (for example, a service A management component, a service B management component, a service C management component). The data storage module, that is, the service function shared database, includes multiple common components, for example, a log shared database (Data Base, DB) function component, a configuration shared DB function component, a statistics shared DB function component, and a data lake function component. The service function module, that is, the service function components, includes public / shared business components (for example, shared service A, shared service B), and business components (for example, service A, service B, service C).

[0034] 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, and service function. Moreover, a shared object repository layer is newly added to achieve decoupling among components of the service. Optionally, components in each layer can be independently deployed on different nodes, and each component can be independently developed using different programming languages and different deployment methods (such as container deployment, virtual server deployment, physical server deployment, etc.). Components in each layer can perform information or data interaction through Representational State Transfer (REST) API interfaces.

[0035] Optionally, in this embodiment, a shared object repository component, i.e., a data sharing module, is introduced to achieve data sharing among services. For example, business component A sends first shared data, and shared business component B sends second shared data to the shared object repository. Through the Publish / Subscribe interaction method, first and second publish messages are generated to prompt the target component (such as business component C that listens to the first and second shared data) to pay attention to the first and second shared data. Specifically, a service can listen to data objects it cares about. After operations such as adding, modifying, and deleting data are performed on the monitored objects, each service will receive a notification, achieving efficient data interaction.

[0036] It should be noted that data sharing through the shared object repository avoids the problem of low efficiency existing in the related art where each service interacts with each other.

[0037] Optionally, in this embodiment, common components that are commonly used by most services are separated and used as a service function sharing database, which can be independently developed, deployed, and maintained. For example, most services will use database functions, statistical functions, logging functions, data analysis functions, message caching functions, etc. Taking the database function as an example, based on different business requirements, different types of databases are used, and different databases have their own different performance tuning methods, different cluster deployments, and data backup methods. By providing shared database software for each service team through common components, each service team only needs to independently develop, deploy, and maintain function components strongly related to its own service, and achieve mutual access through a common REST API interface.

[0038] Optionally, in this embodiment, since each component within the service can be independently deployed, independently expanded, and independently backed up, when any subcomponent has a problem, it will not affect the overall service, and better horizontal expansion can be achieved, which can meet the various needs of users, provide users with better services, and enhance the user experience. For example, only one service management component is needed, but the functional components of the service, i.e., the service body, need three, and only one database is needed, which can be achieved by independently deploying each component, independently expanding, and independently backing up the data.

[0039] Optionally, in this embodiment, the service entity can be redundantly backed up through the business component. Specifically, redundant backup can be performed based on the load balancing of the service. In this case, the service itself will not perform data backup. The service function of multiple instances distributes service requests through the load balancing of the components. When an instance is down, the user re-initiates a request, and the new request will be distributed to the instance in the running state for execution. For example, after backing up the service function component, there are 2 function components in total. When one of the function components is down, the user request will be distributed to the function component that is not down to continue running next time.

[0040] Optionally, when there is a need to back up the service's own data, the service itself can be backed up redundantly through business components. For example, for a certain type of special service that has extremely strong requirements for the consistency of service requests, the service itself supports dynamic data backup, and it is necessary to deploy corresponding redundant backup high availability (HA) instances for it, so that peer nodes can back up services and data for each other. When one is down and the other is up, it can ensure that the user's request is sent to the instance in the up state, avoiding the loss of previous interactive data of the service and the need to re-operate.

[0041] Optional, Figure 4 is an optional architecture diagram of dynamic expansion and backup of service components according to an embodiment of the present invention, such as Figure 4 As shown, the extended service function is multiple instances, that is, through business components, service A is expanded to service A-1, service A-2, service A-3, service A-4, service A-5, and service A-6, and the corresponding high-availability instances are redundantly backed up: A-1-HA, A-2-HA, A-3-HA, A-4-HA, A-5-HA, and A-6-HA.

[0042] Furthermore, a single service management component can manage multiple instances of service functions through a shared object repository. Figure 4As shown in the figure, the above six instances can be managed through the Service A-1 Management Component in the Business Management Component. Among them, the Service A-2 Management Component can be an extended management component based on the Service A-1 Management Component.

[0043] Optionally, all service function instances share the manageable, operable, and displayable data to the Shared Object Warehouse. The single-service management component can then see the objects served and managed by all the extended service function instances, and can operate on the objects served and managed by each instance, achieving effective expansion of the service function instances.

[0044] Specifically, the service function module is also used to obtain the device information of the target device through the business component and the shared business component, and send the device information to the data sharing module, where the target device is the device managed by the business component and the shared business component.

[0045] Optionally, the target device can be the device managed by the business component and the shared business component, and the device information can be information such as the device ID.

[0046] Optionally, in this embodiment, the service components achieve efficient data sharing through the star interaction mode of the Shared Object Warehouse. Specifically, the shared data of the service is published to the Shared Object Warehouse, and all other services concerned about this data can monitor this data.

[0047] Among them, the Shared Object Warehouse can provide the operation mode of Full REST API and the data interaction mechanism of Publish / Subscribe. It can also provide secure link access and Role-Based Access Control (RBAC). The Shared Object Warehouse also supports the mechanisms of data synchronization and active acquisition, supports the characteristics of scalable and redundant backup of data storage, and supports the control of data storage versions.

[0048] Specifically, the service function module is also used to send the interface information of the business component and the shared business component to the data sharing module, so that the service management module can obtain the device information and interface information from the data sharing module, and manage the target device based on the interface information. Optionally, the interface information can be the management interface information for managing the service function component instances. For example, the API interface information for service interaction provided by the business component and the shared business component.

[0049] The present invention will be described below in conjunction with the preferred implementation steps. Figure 2 is a flowchart of an optional microservice management method according to an embodiment of the present invention. As Figure 2 shown, the method includes the following steps:

[0050] Step S201: In response to a first management instruction, generate at least one business component;

[0051] Step S202: Obtain the interface information of at least one business component and send the interface information to the data sharing module;

[0052] Step S203: In response to a second management instruction, obtain the interface information from the data sharing module and manage the target device based on the interface information.

[0053] In the above steps, the first management instruction can be an expansion instruction. Specifically, the expansion is a horizontal expansion of service function body instances. Through service function components, in response to the expansion instruction, at least one business component is generated, such as Service A, Service B, and Service C. The second management instruction can be an information acquisition instruction. Through the service management component, in response to the information acquisition instruction, the interface information, that is, the API interface information provided by Service A, Service B, and Service C for service interaction respectively, can be obtained from the data sharing module, that is, the shared object repository. Thus, the devices managed by Service A, Service B, and Service C respectively can be managed through the API interface information.

[0054] In the embodiment of the present invention, a service layered design method is adopted to completely decouple each component inside the service, that is, each component can be independently deployed, expanded, and data backed up. Through the service management module, the function components included in the service function module can be managed. After expanding a certain service function into multiple instances, through a single service management module, the management of multiple instances of the service function can be realized, and it is more convenient to manage multiple service instances; through the data sharing module, data sharing between services is realized, improving the efficiency of data interaction; through the service function module, the separate expansion and backup of a certain service function can be realized, improving the utilization rate of service resources; through the common components in the data storage module, the common data of business components and shared business components can be stored, realizing the independent deployment and maintenance of function components that most services will use, and serving as common function components for other microservices to directly use without separate selection, development, and maintenance, reducing the repetitive workload of maintenance and development, saving labor costs and time costs, and improving development efficiency.

[0055] It can be seen that through the technical solution of the present invention, the purpose of enabling each component inside the service to be independently deployed, expanded, and data backed up, and completely decoupling each component is achieved through service layered design, thus realizing the technical effect of improving the flexibility of deploying microservices, and further solving the technical problem of poor flexibility in deploying microservices in the existing microservice management system.

[0056] In an alternative embodiment, after generating at least one service component in response to a first management instruction, in response to a connection request sent by a target device, connect at least one service component to the target device; when at least one service component is in a connected state with the target device, obtain device information of the target device through at least one service component and send the device information to a data sharing module.

[0057] In an alternative embodiment, in the process of obtaining interface information from a data sharing module in response to a second management instruction and managing a target device based on the interface information, first respond to the second management instruction to obtain interface information and device information from the data sharing module, and then manage the target device based on the interface information and the device information.

[0058] Optionally, Figure 5 is an application schematic diagram of an alternative microservice management system according to an embodiment of the present invention. As Figure 5 shown, manage a device access point (Point-of-Presence, PoP) through a microservice management system. Specifically, first, through a shared service management component, horizontally start three PoP point service instances in a service function component: PoP point service A, PoP point service B, and PoP point service C, that is, generate at least one service component by the service function component in response to a first management instruction issued by the shared service management component. Among them, the service function body can be configuration management and device management.

[0059] Furthermore, as Figure 5 shown, each PoP point service instance registers its own API for service interaction into a shared object repository, that is, obtain interface information of at least one service component and send the interface information to a data sharing module.

[0060] Furthermore, as Figure 5 shown, all devices in the resource layer are connected to their corresponding PoP point service instances, that is, the devices are respectively 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, connect at least one service component to the target device. Among them, each PoP point service instance can manage up to 3000 devices at most.

[0061] Furthermore, when at least one service component is in a connected state with the target device, PoP point service A, PoP point service B, and PoP point service C synchronously share all registered device information into the shared object repository, that is, obtain device information of the target device through at least one service component and send the device information to a data sharing module.

[0062] Furthermore, as Figure 5As shown in the figure, the PoP point management component can obtain the device information and interface information registered in all "PoP point service" instances from the shared object repository, that is, in response to the second management instruction, obtain the interface information and device information from the data sharing module.

[0063] Furthermore, as Figure 5 shown in the figure, the PoP point management component can see up to 9,000 devices, know which "PoP point service" instance each device belongs to, and can manage them through the service API interface corresponding to the instance, that is, manage the target device based on the interface information and device information.

[0064] It should be noted that in the above process, after the service is cloudified through deployment, it provides guarantee for the interaction between services and better adapts to the business elasticity in the big data era. For the components that can be shared between services, sharing is realized to reduce the development and operation and maintenance costs; the service and data are completely separated, and both can be independently extended and redundantly backed up, not just the whole service, solving the problems in the related technologies that the data is bound to the service, the service extension granularity is too large, and the management and service cannot be separated. The service management, service function and service data are separated from each other, getting rid of the 1:1:1 ratio, and resources can be better allocated according to the actual service request volume and management requirements; the shared object repository component is introduced to realize data sharing between services and ensure the unique storage and integrity of data; by uniformly maintaining common components, the development and maintenance of components are reduced, and service extension is more flexible; each can be independently extended and independently maintained. For example, the database "etcd" can be deployed with three instances as a cluster, and the three instances simultaneously perform data redundancy backup for each other, and the query efficiency can be improved. All services using "etcd" do not need to deploy and maintain "etcd" separately by themselves.

[0065] Thus, through the technical solution of the present invention, the purpose of enabling each component inside the service to be independently deployed, extended and data-backed up, and completely decoupling each component is achieved through service layer design, thereby achieving the technical effect of improving the flexibility of deploying microservices, and further solving the technical problem of poor flexibility in deploying microservices in the existing microservice management system.

[0066] Embodiment 2

[0067] According to an embodiment of the present invention, an embodiment of a microservice management device is provided, wherein, Figure 6 is a schematic diagram of an optional microservice management device according to an embodiment of the present invention, as Figure 6As shown in the figure, the device includes: a first processing module 601, configured to generate at least one service component in response to a first management instruction; an acquisition module 602, configured to acquire interface information of at least one service component and send the interface information to a data sharing module; a second processing module 603, configured to acquire the interface information from the data sharing module in response to a second management instruction and manage a target device based on the interface information.

[0068] It should be noted that the above first processing module 601, acquisition module 602, and second processing module 603 correspond to steps S201 to S203 in the above embodiment. The examples and application scenarios implemented by the three modules and the corresponding steps are the same, but are not limited to the content disclosed in the above embodiment 1.

[0069] Optionally, the microservice management device further includes: a third processing module, configured to connect at least one service component to a target device in response to a connection request sent by the target device; a fourth processing module, configured to obtain device information of the target device through at least one service component and send the device information to the data sharing module when at least one service component and the target device are in a connected state.

[0070] Optionally, the second processing module includes: an acquisition unit, configured to acquire interface information and device information from the data sharing module in response to a second management instruction; a management unit, configured to manage the target device based on the interface information and the device information.

[0071] Optionally, the device access point (PoP) is managed by a microservice management system. Specifically, first, through a shared service management component, three PoP point service instances, namely PoP point service A, PoP point service B, and PoP point service C, are horizontally started in a service function component, that is, at least one service component is generated by the service function component in response to a first management instruction issued by the shared service management component. Each PoP point service instance includes a configuration management component and a device management component.

[0072] Furthermore, each PoP point service instance registers its own API for service interaction into a shared object repository, that is, acquires interface information of at least one service component and sends the interface information to the data sharing module.

[0073] Furthermore, all devices in the resource layer are connected to their corresponding PoP point service instances, that is, the devices are respectively connected to PoP point service A, PoP point service B, and PoP point service C, that is, at least one service component is connected to the target device in response to a connection request sent by the target device. Each PoP point service instance can manage up to 3000 devices at most.

[0074] Further, when at least one service component is in a connected state with the target device, PoP Point Service A, PoP Point Service B, and PoP Point Service C synchronize and share all registered device information to the shared object repository, that is, obtain the device information of the target device through at least one service component and send the device information to the data sharing module.

[0075] Further, the PoP Point management component can obtain the device information and interface information registered in all "PoP Point Service" instances from the shared object repository, that is, in response to the second management instruction, obtain the interface information and device information from the data sharing module.

[0076] Further, the PoP Point management component can view up to 9,000 devices, know which "PoP Point Service" instance each device belongs to, and can manage them through the service API interface corresponding to the instance, that is, manage the target device based on the interface information and device information.

[0077] It should be noted that in the above process, after implementing service cloudification through deployment, it provides guarantee for the interaction between services and better adapts to the business elasticity in the big data era. For the components that can be shared among services, sharing is achieved to reduce the development and operation and maintenance costs; the service and data are completely separated, and both can be independently expanded and redundantly backed up, not just the overall service, solving the problems in related technologies where data is bound to the service, the service expansion granularity is too large, and management and service cannot be separated. The service management, service function, and service data are separated from each other, getting rid of the 1:1:1 ratio, and resources can be better allocated according to the actual service request volume and management requirements; the shared object repository component is introduced to achieve data sharing among services and ensure the unique storage and integrity of data; by uniformly maintaining common components, the development and maintenance of components are reduced, and service expansion is more flexible; each can be independently expanded and independently maintained. For example, the database "etcd" can be deployed with three instances as a cluster, and the three instances perform data redundancy backup for each other at the same time, and the query efficiency can be improved. All services using "etcd" do not need to deploy and maintain "etcd" separately by themselves.

[0078] Embodiment 3

[0079] 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, and the computer program is configured to execute the above-mentioned microservice management method when running.

[0080] Embodiment 4

[0081] According to another aspect of the embodiments of the present invention, an electronic device is further provided. The electronic device includes one or more processors; a memory for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement a program for running, wherein the program is configured to execute the above-mentioned microservice management method when running.

[0082] Embodiment 5

[0083] According to another aspect of the embodiments of the present invention, a computer program product is further provided, including a computer program / instructions, and when the computer program / instructions are executed by a processor, the above-mentioned microservice management method is implemented.

[0084] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0085] In the above embodiments of the present invention, the descriptions of the various embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

[0086] In the several embodiments provided by the present application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only illustrative. For example, the division of the units can be a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the units or modules can be in an electrical or other form.

[0087] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

[0089] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The foregoing storage medium includes: various media such as USB flash drives, read-only memories (ROMs), random access memories (RAMs), mobile hard disks, magnetic disks, or optical discs that can store program codes.

[0090] The foregoing are only the preferred embodiments of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present invention, several improvements and modifications can be made, and these improvements and modifications should also be regarded as the protection scope of the present invention.

Claims

1. A microservice management system, characterized in that, Including: A service management module for managing functional components included in a service function module, where the functional components at least include business components and shared business components; A data sharing module for receiving first shared data sent by the business components and second shared data sent by the shared business components, and generating first release information and second release information based on the first shared data and the second shared data, where the first release information and the second release information are used to prompt target components to pay attention to the first shared data and the second shared data, and the target components are components in the business components and the shared business components that listen to the first shared data and the second shared data; A data storage module including at least one common component for storing common data of the business components and the shared business components through the at least one common component; The service function module for responding to a management instruction sent by the service management module and performing a target operation based on the management instruction, where the management instruction includes at least one of the following: an expansion instruction, a backup instruction, and the target operation includes at least one of the following: an expansion operation, a 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 business components and the shared business components and send the device information to the data sharing module, where the target device is a device managed by the business components and the shared business components.

3. The system according to claim 2, wherein The service function module is further configured to send interface information of the business components and the shared business components 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, characterized in that, The microservice management method is applied to the microservice management system according to any one of claims 1 to 3 and includes: Responding to a first management instruction to generate at least one business component; Obtaining interface information of the at least one business component and sending the interface information to the data sharing module; Responding to a second management instruction, obtaining the interface information from the data sharing module, and managing a target device based on the interface information.

5. The method according to claim 4, characterized in that, After responding to the first management instruction to generate at least one business component, the method further includes: Responding to a connection request sent by the target device to connect the at least one business component to the target device; When the at least one business component and the target device are in a connected state, obtaining device information of the target device through the at least one business component and sending the device information to the data sharing module.

6. The method according to claim 5, characterized in that, Responding to a second management instruction, obtaining the interface information from the data sharing module, and managing a target device based on the interface information includes: Responding to a second management instruction, obtaining the interface information and the device information from the data sharing module; Managing the target device based on the interface information and the device information.

7. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the microservice management method described in any one of claims 4 to 6 when running.

8. An electronic device, characterized in that, The electronic device includes 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 program for running, wherein the program is configured to execute the microservice management method described in any one of claims 4 to 6 when running.

9. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by a processor, the microservice management method described in any one of claims 4 to 6 is implemented.

Images