CN111552672B - Distributed service state consistency maintenance method and device based on ZooKeeper - Google Patents
Distributed service state consistency maintenance method and device based on ZooKeeper Download PDFInfo
- Publication number
- CN111552672B CN111552672B CN202010102586.8A CN202010102586A CN111552672B CN 111552672 B CN111552672 B CN 111552672B CN 202010102586 A CN202010102586 A CN 202010102586A CN 111552672 B CN111552672 B CN 111552672B
- Authority
- CN
- China
- Prior art keywords
- node
- service
- instance
- name
- nodes
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
Abstract
The invention provides a ZooKeeper-based distributed service state consistency maintenance method and a ZooKeeper-based distributed service state consistency maintenance device, wherein the implementation process comprises the following steps: the service registry creates a root node of the global data space on the ZooKeeper cluster; when executing service registration operation, the service registration center creates a name space node, a service name node, a version number node and an instance node under the root node of the ZooKeeper cluster according to the name space and version number information of the service; the service provider and service consumer create service provider nodes and service consumer nodes under the instance nodes of the ZooKeeper cluster global data space during the initialization phase of service operation. The invention can efficiently and globally and consistently maintain the static basic information of the service by utilizing the persistent node characteristic of the ZooKeeper, acquire the survival condition of the service provider and the access condition of the service consumer to the service instance in real time, and provide a foundation for realizing dynamic binding of the service, load balancing of the service request, real-time monitoring of the system and the like.
Description
Technical Field
The invention belongs to the technical field of computers, relates to a service load balancing technology, and particularly relates to a distributed service state consistency maintenance method and device based on a ZooKeeper.
Background
In the early stage of service integration framework application, a single-machine centralized architecture is adopted in a service registry, and the framework can basically meet application requirements due to smaller service scale. However, with the deep practice of service, more and more applications are integrated, and the shortcomings of the single-machine centralized service registry in terms of performance, fault tolerance and expandability are gradually exposed.
In order to solve the problem existing in the single-machine centralized service registry, the original service registry needs to be changed into a distributed cluster architecture. Because distributed service registry clusters need to share data, an efficient data synchronization scheme is needed for maintaining data consistency among service registry clusters.
Disclosure of Invention
In order to overcome the defects of the prior art, the inventor performs intensive research and provides a ZooKeeper-based distributed service state consistency maintenance method and device, and a global data space is constructed by utilizing a ZooKeeper file system so as to maintain the data consistency of a distributed service registry cluster in a service integration framework; the ZooKeeper persistent node is used for maintaining the same name service under different namespaces and different version information of the same service, so that different versions of the service can be simultaneously accommodated in the system and the service can be simultaneously provided for service consumers; by using the temporary node to maintain the survival condition of each service and service consumers in the system, a system administrator can obtain the consistent real-time state information of all service providers and corresponding service consumers distributed in the system by traversing the global data space, thereby realizing the global real-time monitoring of the system and completing the invention.
The invention aims to provide the following technical scheme:
in a first aspect, a ZooKeeper-based distributed service state consistency maintenance method includes:
s100, a service registry creates a root node of a global data space on a ZooKeeper cluster;
s200, when a service registration operation is executed, a service registration center creates a name space node, a service name node, a version number node and an instance node under a root node of a ZooKeeper cluster according to name space and version number information of a service, wherein the instance node is divided into a service provider instance node and a service consumer instance node.
Further, the method includes S300, where the service provider and the service consumer create a service provider node and a service consumer node under an instance node of the ZooKeeper cluster global data space at an initialization stage of service operation, the service provider node having the service provider instance node as a parent node, and the service consumer node having the service consumer instance node as a parent node.
In a second aspect, a ZooKeeper-based distributed service state consistency maintenance device includes: the service registry is used for creating a root node of the global data space on the ZooKeeper cluster, and creating a name space node, a service name node, a version number node and an instance node under the root node of the ZooKeeper cluster according to the name space and the version number information of the service;
wherein the instance nodes are divided into service provider instance nodes and service consumer instance nodes.
Further, the apparatus further comprises:
a service provider for creating a service provider node under a service provider instance node of a ZooKeeper cluster global data space at an initialization stage of service operation;
a service consumer for creating a service consumer node under a service consumer instance node of a ZooKeeper cluster global data space at an initialization stage of service operation.
The distributed service state consistency maintenance method and device based on the ZooKeeper provided by the invention have the beneficial technical effects that:
the invention uses the ZooKeeper cluster to maintain the data consistency of the global data space, and solves the data synchronization problem generated when the service registration center is converted from a single-machine centralized architecture into a distributed cluster architecture. By utilizing the persistent node characteristics of the ZooKeeper, the static basic information of the service can be efficiently and globally and consistently maintained; by utilizing the temporary node characteristics of the ZooKeeper, the survival condition of the service provider and the access condition of the service consumer to the service provider can be obtained in real time, and a foundation is provided for realizing dynamic binding of the service, load balancing of the service request, real-time monitoring of the system and the like.
Drawings
FIG. 1 shows a ZooKeeper global data space architecture diagram proposed by the present invention;
FIG. 2 is a flowchart showing a service registration process in embodiment 2;
fig. 3 shows a service provider and service consumer survival monitoring diagram in embodiment 3.
Detailed Description
The invention introduces a ZooKeeper as a medium for maintaining data consistency.
The implementation goal of the ZooKeeper is to solve the distributed consistency problem. In a distributed environment, consistency is a property that refers to whether consistency can be maintained among multiple service providers. The ZooKeeper server generally provides data updating and inquiring functions in a peer-to-peer cluster mode, so that the ZooKeeper can work normally as long as more than half of members in the cluster survive, the client can update any one server in the cluster, the result can be synchronized to other servers after the operation is successful, and all the clients can inquire consistent and effective data.
In order to reasonably utilize the data storage mode of the ZooKeeper cluster file system to adapt to the management of service providers and service consumers by the service registry, the data storage structure of the service providers and the service consumers needs to be designed. Because a large number of different service providers exist in the original service integration framework system, the service providers can be given the same name due to different developers, so as to distinguish different services with the same name, and allow the services with the same name to exist under different namespaces respectively, thereby expanding the service naming mechanism of the service integration framework system. In addition, since the developer can update the functions of the service provider and repair vulnerabilities regularly, for the same service provider, there may be iterative versions of different periods in the system, and the service consumer may need to use different versions of the service according to the own needs, so the service integration framework allows the developer to upload different versions of the same service and distinguish by version numbers. Further, knowing the survival condition of the service provider and the access condition of the service consumer to the service provider is very important to realize dynamic binding of the service, load balancing of the service request, real-time monitoring of the system and the like, so that the data storage mode of the ZooKeeper cluster file system is preferably utilized to realize real-time grasping of the survival condition of the provider and the access condition of the service consumer to the service provider.
The invention is further described in detail below by means of the figures and examples. The features and advantages of the present invention will become more apparent from the description.
As shown in fig. 1, according to a first aspect of the present invention, there is provided a ZooKeeper-based distributed service state consistency maintenance method, including:
s100, a service registry creates a root node of a global data space on a ZooKeeper cluster;
s200, when a service registration operation is executed, a service registration center creates a name space node, a service name node, a version number node and an instance node under a root node of a ZooKeeper cluster according to name space and version number information of a service, wherein the instance node is divided into a service provider instance node and a service consumer instance node;
in the present invention S200, the root node is the parent node of the namespace node, the namespace node is the parent node of the service name node, the service name node is the parent node of the version number node, and the version number node is the parent node of the instance node.
Further, one or more namespace nodes may be created under the root node, one or more service name nodes may be created under each namespace node, one or more version number nodes may be created under each service name node, one service provider instance node and one service consumer instance node may be created under each version number node.
The name space node is used for distinguishing the same name service; the service name node is used for distinguishing services with different functions; the version number node is used for distinguishing iteration versions of the same service in different periods; the service provider instance nodes in the instance nodes are for hosting a service provider node list, and the service consumer instance nodes are for hosting a service consumer node list.
In the invention, the service with the same name can exist under different name space nodes, and in this way, the service with the same name and different functions can be maintained in the system.
In the invention, the same service with different versions can exist under different service version number nodes, different versions of the same service can be maintained in this way, and the version of the service can be dynamically increased through the service registration operation of the service registration center.
Further, the executable file of the service provider is stored on the version number node of the ZooKeeper cluster global data space, wherein the executable file refers to a compressed package of the minimum environment required by the executable program and the running of the executable program, which is written and compiled by a developer, and the executable file is stored on the version number node, and has the advantages that: the storage structure of the Zookeeper cluster may be used to store service provider identification information, where the service provider identification refers to the name space, service name, and version number information where the service provider is located, and these information may uniquely identify a service provider.
In a preferred embodiment of the present invention, the namespace node, the service name node, the version number node, and the instance node are persistent nodes. The namespace node, the service name node, the version number node, and the instance node may also be set as temporary nodes as persistent nodes, however, the reason for setting as persistent nodes is that: these static service provider information are pruned less frequently and accessed more frequently, and their presence does not require hooking with an application.
In the invention, when a service registration center executes service registration operation, if a service with the same service name exists under a namespace node, a ZooKeeper cluster prompts that the service name is repeated, and the service registration center registers the service under the namespace node by modifying the service name of the newly registered service; alternatively, a new namespace node is created on the ZooKeeper cluster under which registration of the service is performed.
In the present invention, the maintenance method further includes S300, when the service is running, the service provider and the service consumer create a service provider node and a service consumer node under an instance node of the ZooKeeper cluster global data space in an initialization phase of the service running, the service provider node takes the service provider instance node as a parent node, and the service consumer node takes the service consumer instance node as a parent node. Further, one or more service provider nodes may be created under the service provider instance node, and one or more service consumer nodes may be created under the service consumer instance node.
The service provider node is created and used for monitoring the survival condition of the service provider in real time and receiving the monitoring information of the service provider, and the service consumer node is used for monitoring the number of running service consumers in the service integration framework and the condition of calling the service provider in real time.
In a preferred embodiment of the invention, the created service provider node and service consumer node are temporary nodes. The service provider and the service consumer maintain the connection of the temporary nodes corresponding to the ZooKeeper cluster global data space through heartbeat messages during the operation period, and the temporary nodes are automatically deleted once the application program is closed.
The reason why the creation service provider node and the service consumer node may be temporary nodes or persistent nodes is that: the service provider node and the service consumer node are in one-to-one correspondence with the service provider and the service consumer application program, and according to the characteristics of the ZooKeeper temporary node, the service provider node and the service consumer node are linked with the service provider and the service consumer application program through heartbeat messages, and the nodes are automatically deleted once the application program is closed, so that the survival condition of the service provider and the service consumer application program is monitored.
In the invention, the organization architecture of the ZooKeeper cluster global data space maintains a plurality of information such as a service name space, a service name, a service version number, a service instance and the like, thereby efficiently completing the data synchronization of the distributed service registration center cluster.
According to a second aspect of the present invention, there is provided a ZooKeeper-based distributed service state consistency maintenance apparatus, comprising:
the service registry is used for creating a root node of the global data space on the ZooKeeper cluster, and creating a name space node, a service name node, a version number node and an instance node under the root node of the ZooKeeper cluster according to the name space and the version number information of the service;
wherein the instance nodes are divided into service provider instance nodes and service consumer instance nodes.
In the present invention S200, the root node is the parent node of the namespace node, the namespace node is the parent node of the service name node, the service name node is the parent node of the version number node, and the version number node is the parent node of the instance node.
Further, one or more namespace nodes may be created under the root node, one or more service name nodes may be created under each namespace node, one or more version number nodes may be created under each service name node, one service provider instance node and one service consumer instance node may be created under each version number node.
Still further, the namespace node, the service name node, the version number node, and the instance node are persistent nodes.
In the invention, the device further comprises:
a service provider for creating a service provider node under a service provider instance node of a ZooKeeper cluster global data space at an initialization stage of service operation;
a service consumer for creating a service consumer node under a service consumer instance node of a ZooKeeper cluster global data space at an initialization stage of service operation.
Further, one or more service provider nodes may be created under the service provider instance node, and one or more service consumer nodes may be created under the service consumer instance node.
Still further, the created service provider node and service consumer node are temporary nodes.
The implementation principle and the technical effect of the device in the invention are similar, and the corresponding technical scheme for executing the method is not repeated here.
Those skilled in the art will appreciate that: all or part of the steps for implementing the above method may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer-readable storage medium. The program, when executed, performs steps comprising the method described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
Examples
Example 1
As shown in fig. 1, the invention is realized by the following technical scheme: a distributed service state consistency maintenance method based on ZooKeeper is mainly divided into two parts:
the task of the first part is the construction and maintenance of a ZooKeeper cluster global data space persistent node, which is used for storing basic information of developed services in a service integration framework system, and comprises the following steps of:
(1) The service registry creates root node servers of the global data space on the ZooKeeper cluster;
(2) When executing service registration operation, the service registration center creates corresponding lasting nodes under the root node according to the information of the name space, version number and the like of the service: namespace nodes seu and sat; service name node Radar under the name space node seu and service name node Sonar under the name space node sat; the service version comprises 1.0 and 2.0 versions, so that two version number nodes are created under a service name node Radar, two instance nodes are created under the latest version number node, and a service provider instance node (providers instance node) and a service consumer instance node (consumers instance node);
(3) And storing the executable file of the service on a version number node of the ZooKeeper cluster global data space.
The task of the second part is the dynamic maintenance of the service provider and service consumer survival state, maintaining a connection with the service provider and service consumer processes through the temporary nodes of the ZooKeeper cluster global data space, mainly comprising the following steps:
(1) The service provider and the service consumer create corresponding temporary nodes in the ZooKeeper cluster global data space in the service running initialization stage: the service providers Radar1 and Radar2 create a Radar1 temporary node and a Radar2 temporary node under the providers instance node; the service consumer sil creates a sil temporary node under the Consumers instance node;
(2) The service provider and the service consumer maintain the connection with the temporary node of the ZooKeeper cluster global data space through a heartbeat message during the operation period, and the temporary node is automatically deleted once the application program is closed.
Example 2
The flow shown in fig. 2 consists of a service registry, service consumers and service instances, the service registry creating persistent nodes, maintaining basic information of the service. The service provider creates a temporary node with the service consumer, maintaining the survival state of the service provider and the service consumer. The entire flow starts with service registration.
In the embodiment operation flow shown in fig. 2, a service named Radar exists in the original system, two service versions 1.0 and 2.0 exist, and the service of version 1.0 named Sonar is registered under a sat namespace node of a ZooKeeper global data space. Alternatively, since there is no service under the seu namespace node that is the same name as the service Sonar, it may also be registered under the seu namespace node.
Example 3
In the operational flow shown in fig. 3, two service providers of version 2.0 of the Radar service are first run and the service consumer sid is bound to the service provider Radar 1. After the Radar1 service is closed, the temporary nodes of the ZooKeeper global data space are deleted and the service consumer is rebind to the service provider Radar 2.
The invention has been described above in connection with preferred embodiments, which are, however, exemplary only and for illustrative purposes. On this basis, the invention can be subjected to various substitutions and improvements, and all fall within the protection scope of the invention.
Claims (6)
1. A distributed service state consistency maintenance method based on ZooKeeper is characterized by comprising the following steps:
s100, a service registry creates a root node of a global data space on a ZooKeeper cluster;
s200, when a service registration operation is executed, a service registration center creates a name space node, a service name node, a version number node and an instance node under a root node of a ZooKeeper cluster according to name space and version number information of a service, wherein the instance node is divided into a service provider instance node and a service consumer instance node; the root node is a father node of the name space node, the name space node is a father node of the service name node, the service name node is a father node of the version number node, and the version number node is a father node of the instance node; the naming space node is used for distinguishing the same name service; the service name node is used for distinguishing services with different functions; the version number node is used for distinguishing iteration versions of the same service in different periods; service provider instance nodes in the instance nodes are used for storing service provider node lists, and service consumer instance nodes are used for storing service consumer node lists;
the name space node, the service name node, the version number node and the instance node are persistent nodes; the executable file of the service provider is stored on a version number node of the ZooKeeper cluster global data space;
s300, a service provider and a service consumer establish a service provider node and a service consumer node under an instance node of a ZooKeeper cluster global data space in an initialization stage of service operation, wherein the service provider node takes the service provider instance node as a father node, the service consumer node takes the service consumer instance node as a father node, and the service provider node and the service consumer node are temporary nodes.
2. The method of claim 1, wherein in S200, one or more namespace nodes may be created under the root node, one or more service name nodes may be created under each namespace node, one or more version number nodes may be created under each service name node, and one service provider instance node and one service consumer instance node may be created under each version number node.
3. The method of claim 1, wherein when a service registration operation is performed by a service registration center, if a service with the same service name already exists under a namespace node, the ZooKeeper cluster prompts that the service name is repeated, and the service registration center registers the service under the namespace node by modifying the service name of the newly registered service; alternatively, a new namespace node is created on the ZooKeeper cluster under which registration of the service is performed.
4. A ZooKeeper-based distributed service state consistency maintenance device, comprising:
the service registry is used for creating a root node of the global data space on the ZooKeeper cluster, and creating a name space node, a service name node, a version number node and an instance node under the root node of the ZooKeeper cluster according to the name space and the version number information of the service;
the instance nodes are divided into service provider instance nodes and service consumer instance nodes; the root node is a father node of the name space node, the name space node is a father node of the service name node, the service name node is a father node of the version number node, and the version number node is a father node of the instance node; the naming space node is used for distinguishing the same name service; the service name node is used for distinguishing services with different functions; the version number node is used for distinguishing iteration versions of the same service in different periods; service provider instance nodes in the instance nodes are used for storing service provider node lists, and service consumer instance nodes are used for storing service consumer node lists;
the name space node, the service name node, the version number node and the instance node are persistent nodes; the executable file of the service provider is stored on the version number node of the ZooKeeper cluster global data space
Wherein the instance nodes are divided into service provider instance nodes and service consumer instance nodes.
5. The apparatus of claim 4, wherein the apparatus further comprises:
a service provider for creating a service provider node under a service provider instance node of a ZooKeeper cluster global data space at an initialization stage of service operation;
a service consumer for creating a service consumer node under a service consumer instance node of a ZooKeeper cluster global data space at an initialization stage of service operation.
6. The apparatus of claim 5, wherein one or more namespace nodes may be created under the root node, one or more service name nodes may be created under each namespace node, one or more version number nodes may be created under each service name node, one service provider instance node and one service consumer instance node may be created under each version number node;
one or more service provider nodes may be created under the service provider instance node and one or more service consumer nodes may be created under the service consumer instance node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010102586.8A CN111552672B (en) | 2020-02-19 | 2020-02-19 | Distributed service state consistency maintenance method and device based on ZooKeeper |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010102586.8A CN111552672B (en) | 2020-02-19 | 2020-02-19 | Distributed service state consistency maintenance method and device based on ZooKeeper |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111552672A CN111552672A (en) | 2020-08-18 |
| CN111552672B true CN111552672B (en) | 2023-09-15 |
Family
ID=72004057
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010102586.8A Active CN111552672B (en) | 2020-02-19 | 2020-02-19 | Distributed service state consistency maintenance method and device based on ZooKeeper |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111552672B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114697231B (en) * | 2020-12-31 | 2023-08-01 | 电科云(北京)科技有限公司 | Gateway-based service discovery and service registration method and device |
| CN115277714B (en) * | 2021-04-29 | 2023-08-15 | 中国移动通信集团浙江有限公司 | Method, device, equipment and computer readable storage medium for repairing service registration abnormality |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107172230A (en) * | 2017-07-24 | 2017-09-15 | 北京赛特斯信息科技股份有限公司 | The method that service node address is found is realized based on third party database |
| CN108228393A (en) * | 2017-12-14 | 2018-06-29 | 浙江航天恒嘉数据科技有限公司 | A kind of implementation method of expansible big data High Availabitity |
| CN109067841A (en) * | 2018-07-05 | 2018-12-21 | 武汉斗鱼网络科技有限公司 | Service current-limiting method, system, server and storage medium based on ZooKeeper |
| CN109992354A (en) * | 2019-04-09 | 2019-07-09 | 腾讯科技（深圳）有限公司 | Container-treatment, device, principal server, system and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11128578B2 (en) * | 2018-05-21 | 2021-09-21 | Pure Storage, Inc. | Switching between mediator services for a storage system |
-
2020
- 2020-02-19 CN CN202010102586.8A patent/CN111552672B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107172230A (en) * | 2017-07-24 | 2017-09-15 | 北京赛特斯信息科技股份有限公司 | The method that service node address is found is realized based on third party database |
| CN108228393A (en) * | 2017-12-14 | 2018-06-29 | 浙江航天恒嘉数据科技有限公司 | A kind of implementation method of expansible big data High Availabitity |
| CN109067841A (en) * | 2018-07-05 | 2018-12-21 | 武汉斗鱼网络科技有限公司 | Service current-limiting method, system, server and storage medium based on ZooKeeper |
| CN109992354A (en) * | 2019-04-09 | 2019-07-09 | 腾讯科技（深圳）有限公司 | Container-treatment, device, principal server, system and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 张鹏飞 ; .分布式服务框架的设计与实现.现代计算机(专业版).2018,(10),正文2.3节. * |
| 苟丽美 ; 张锋叶 ; 林国华 ; .基于Zookeeper的GIS集群实现.计算机工程与设计.2017,(09),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111552672A (en) | 2020-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2425977C (en) | Realtime configuration updates and software distribution to active client positions | |
| CN111865900B (en) | RPC protocol-based cross-network regional proxy access method and system | |
| CN106663033B (en) | System and method for supporting a wraparound domain and proxy model and updating service information for cross-domain messaging in a transactional middleware machine environment | |
| CN111552672B (en) | Distributed service state consistency maintenance method and device based on ZooKeeper | |
| CN111026414B (en) | HDP platform deployment method based on kubernetes | |
| CA2686384C (en) | Dynamic cli mapping for clustered software entities | |
| CN113778623B (en) | Resource processing method and device, electronic equipment and storage medium | |
| CN111897541B (en) | Software interaction platform and method for automatically deploying resources in cloud environment | |
| JP2015512091A (en) | Coordinating processes in a cloud computing environment | |
| US20050278385A1 (en) | Systems and methods for staggered data replication and recovery | |
| CN112882792B (en) | Information loading method, computer device and storage medium | |
| US20200403872A1 (en) | Pod migration across nodes of a cluster | |
| CN114363402B (en) | Shooting range interconnection method, shooting range interconnection system and electronic equipment | |
| US20030237081A1 (en) | Updating an application using database replication | |
| Meehean et al. | A service migration case study: Migrating the Condor schedd | |
| CN111897551A (en) | Platform and method for rapidly cloning software environment in cloud environment | |
| WO2024021471A1 (en) | Service updating method, apparatus and system, and storage medium | |
| CN116155978A (en) | Multi-registry adaptation method, device, electronic equipment and storage medium | |
| Lüer et al. | The evolution of software evolvability | |
| US8495634B2 (en) | Method for the management of tasks in a decentralized data network | |
| CN113485828A (en) | Distributed task scheduling system and method based on quartz | |
| US9588861B2 (en) | Method and apparatus for automatically identifying components to monitor in an enterprise environment | |
| CN115604101B (en) | System management method and related equipment | |
| CN113434283B (en) | Service scheduling method and device, server and computer readable storage medium | |
| US8706796B2 (en) | Managing a cluster of computers |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |