CN111431985B - Method for synchronizing resource states among cloud service heterogeneous subsystems - Google Patents
Method for synchronizing resource states among cloud service heterogeneous subsystems Download PDFInfo
- Publication number
- CN111431985B CN111431985B CN202010192901.0A CN202010192901A CN111431985B CN 111431985 B CN111431985 B CN 111431985B CN 202010192901 A CN202010192901 A CN 202010192901A CN 111431985 B CN111431985 B CN 111431985B
- Authority
- CN
- China
- Prior art keywords
- resource
- management layer
- service
- service cluster
- server
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention provides a method for synchronizing resource states among cloud service heterogeneous subsystems, which comprises a resource creation method and a resource state query method, wherein the resource creation method comprises the following steps: a user orders and creates resources through a UI interface or an openapi, and a transmission-server service in an operation management layer service cluster receives a request; after receiving the request, the resource-server service in the resource management layer service cluster stores a database instance table, and sends the request to a resource module to create a resource; the schedule scheduling service in the resource management layer service cluster looks at the state of creating resources to the resource module every 30 seconds and updates the local library. The method for synchronizing the resource states among cloud service heterogeneous subsystems provides a method with high efficiency, stability and high concurrency support for synchronizing the resource states among the layered-deployment native cloud architectures.
Description
Technical Field
The invention belongs to the field of cloud computing, and particularly relates to a method for synchronizing resource states among cloud service heterogeneous subsystems.
Background
Cloud computing is to server resources such as computation, network, storage and the like, and provides a distributed computing mode of different resources according to requirements of different tenants and users. With the development of technology, more and more enterprises and individuals nowadays start to purchase and use cloud computing services due to the excessive cost of purchasing hardware resources, and the public cloud market is growing rapidly.
In order to provide more resources and computing power for more tenants and users and improve stability of resources and security of user data, most common cloud manufacturers at home and abroad mostly adopt to deploy a plurality of data centers in different regions to provide resource services for the tenants and users respectively. However, for tenants and users, the resources purchased in all regions need to be seen for convenient management, and a service needs to be provided to collect the resource information of all region services, which brings a problem about how to synchronize the states of the resources in the subsystems of the cloud service architecture.
The existing synchronization scheme between heterogeneous systems is roughly divided into two types, one is a message middleware MQ, and when data of a data changing party changes, a data receiving party is informed to update the changed data through a queue; and the other is to provide an API interface between heterogeneous systems, and directly call the API interface to update data when the data changes. Both of these solutions suffer from drawbacks: the MQ is used for data synchronization, and depending on network states among heterogeneous systems, the MQ has high requirements on network stability and also has the risk of losing messages, and if the messages are lost, the risk that the data can not be automatically synchronized forever can exist; synchronization through the API interface may have cyclic dependencies between two heterogeneous systems and increase the coupling between heterogeneous systems with poor performance and concurrency support.
Summary of the invention
In view of the above, the invention aims to provide a method for synchronizing resource states among heterogeneous cloud service subsystems, and provides an efficient and stable method for synchronizing resource states among layered-deployment native cloud architectures.
In order to achieve the above purpose, the technical scheme of the invention is realized as follows:
a method for synchronizing resource states among cloud service heterogeneous subsystems comprises a resource creation method and a resource state query method, wherein the resource creation method comprises the following steps:
a1, a user orders and creates resources through a UI interface or an openapi, and a transmission-server service in an operation management layer service cluster receives a request;
a2, after receiving the request, the transaction-server service in the operation management layer service cluster calls the resource-server service in the operation management layer service cluster, and the resource-server service stores a database instance table and sends the request to the resource-server service in the resource management layer service cluster to request for creating resources;
a3, after receiving the request, the resource-server service in the resource management layer service cluster stores a database instance table, and sends the request to a resource module to create a resource;
a4, checking the state of creating the resource to a resource module every 30 seconds by using a schedule scheduling service in the resource management layer service cluster, and updating a local library;
a5, the schedule scheduling service in the operation management layer service cluster acquires the created resource state from the resource-server service in the resource management layer service cluster every 30 seconds, and updates the local library;
the resource state query method comprises the following steps:
b1, a user inquires the resource state through a UI interface or an openapi, and a resource-server in an operation management layer service cluster receives a request;
b2, after receiving the request, the resource-server in the operation management layer service cluster directly acquires the state information from the local library instance table and returns the state information;
b3, after receiving the request, judging whether the redis cache has synchronous records or not, and if the synchronous records do not have the state of asynchronously calling the resource-server synchronous resources in the resource management layer service cluster; the life cycle of synchronous record in the redis cache is 15s;
and B4, the schedule scheduling service in the operation management layer service cluster regularly calls the resource-server in the resource management layer service cluster to synchronize the states of all resources.
Further, in step A1, the transaction-server service in the operation management layer service cluster is used for taking charge of operations related to user transactions, including order placing and order returning.
Further, in step A2, the resource-server service in the operation management layer service cluster is used for responsible for resource management, including a resource list and resource details;
the operation management layer service cluster manages a plurality of resource management layer service clusters, and integrates resource information of users distributed on a plurality of resource modules.
Further, in step A2, the database instance table in the service cluster of the operation management layer is used to store the basic information of resources of all users distributed in all resource modules.
Further, in step A3, a resource-server service in the resource management layer service cluster is used for resource management, including a resource list and resource details;
each resource module corresponds to a resource management layer service cluster.
Further, in step A3, the resource management layer serves a database instance table in the cluster to store the basic information of the resources corresponding to the resource module.
Further, in step A4, the schedule scheduling service in the resource management layer service cluster is configured to send a request to the resource module every 30 seconds, obtain the states of all resources in the non-deleted and non-created failure states according to the states in the instance table, and update the local library;
the schedule scheduling service in the resource management layer service cluster is also used for updating the resource status as the creation failure when the resource status is in the creation for more than 30 minutes when the resource is created.
Further, in step B2, after receiving the request, the resource-server service in the service cluster of the operation management layer directly obtains the status information from the local library and returns the status information;
wherein the status returned is determined based on status and opt_status.
Further, in step B3, the redis-server service in the service cluster of the operation management layer is used for caching distributed data;
the record of the synchronous state in the redis cache is cached for 15s.
Further, in step B4, the schedule scheduling service in the service cluster of the operation management layer obtains the resource status of the service cluster of the specified resource management layer every hour, so as to avoid the situation that the long-time resource status is inconsistent due to the fact that the user does not manually operate to obtain the instance status for a long time.
Compared with the prior art, the method for synchronizing the resource states among cloud service heterogeneous subsystems has the following advantages:
the method for synchronizing the resource states among cloud service heterogeneous subsystems provides a method with high efficiency, stability and high concurrency support for synchronizing the resource states among the layered-deployment native cloud architectures.
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 specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute an undue limitation on the invention. In the drawings:
FIG. 1 is a schematic diagram of an organization architecture according to an illustrative embodiment of the invention;
FIG. 2 is a flow diagram illustration of resource creation in accordance with an inventive embodiment of the present invention;
FIG. 3 is a flowchart illustration of a resource status query according to an embodiment of the present invention.
Detailed Description
It should be noted that, without conflict, the embodiments of the present invention and features of the embodiments may be combined with each other.
In the description of the invention, it should be understood that the terms "center," "longitudinal," "transverse," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," and the like indicate orientations or positional relationships that are based on the orientation or positional relationships shown in the drawings, merely to facilitate describing the invention and simplify the description, and do not indicate or imply that the device or element being referred to must have a particular orientation, be configured and operate in a particular orientation, and therefore should not be construed as limiting the invention. Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first", "a second", etc. may explicitly or implicitly include one or more such feature. In the description of the invention, unless otherwise indicated, the meaning of "a plurality" is two or more.
In the description of the invention, it should be noted that, unless explicitly specified and limited otherwise, the terms "mounted," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the above terms in the creation of the present invention can be understood by those of ordinary skill in the art in a specific case.
The invention will be described in detail below with reference to the drawings in connection with embodiments.
As shown in fig. 1 to 3, a method for synchronizing resource states among heterogeneous subsystems of a cloud service includes a resource creation method and a resource state query method, wherein the resource creation method includes the following steps:
the resource creation method comprises the following steps:
a1, a user orders and creates resources through a UI interface or an openapi, and a transmission-server service in an operation management layer service cluster receives a request;
a2, after receiving the request, the transaction-server service in the operation management layer service cluster calls the resource-server service in the operation management layer service cluster, and the resource-server service stores a database instance table and sends the request to the resource-server service in the resource management layer service cluster to request for creating resources;
a3, after receiving the request, the resource-server service in the resource management layer service cluster stores a database instance table, and sends the request to a resource module to create a resource;
a4, checking the state of creating the resource to a resource module every 30 seconds by using a schedule scheduling service in the resource management layer service cluster, and updating a local library;
a5, the schedule scheduling service in the operation management layer service cluster acquires the created resource state from the resource-server service in the resource management layer service cluster every 30 seconds, and updates the local library;
the resource status query includes the steps of:
b1, a user inquires the resource state through a UI interface or an openapi, and a resource-server in an operation management layer service cluster receives a request;
b2, after receiving the request, the resource-server in the operation management layer service cluster directly acquires the state information from the local library instance table and returns the state information;
b3, after receiving the request, judging whether the redis cache has synchronous records or not, and if the synchronous records do not have the state of asynchronously calling the resource-server synchronous resources in the resource management layer service cluster; the life cycle of synchronous record in the redis cache is 15s;
b4, scheduling service in the operation management layer service cluster regularly calls resource-server in the resource management layer service cluster to synchronize the states of all resources;
in step A1, the transaction-server service in the operation management layer service cluster is mainly responsible for operations related to user transactions, such as order placing, order returning, and the like.
In step A2, resource-server service in the operation management layer service cluster is mainly responsible for resource management, including operations such as resource list, resource details and the like; the operation management layer service cluster manages a plurality of resource management layer service clusters, and integrates resource information of users distributed on a plurality of resource modules.
In step A2, a database instance table in the service cluster of the operation management layer mainly stores the basic information of resources of all users distributed in all resource modules; the id column in the Instance table is the table primary key; the instance_id column is the resource id; order_id is the id of the user's order, allowing multiple resources to be created in one order, i.e., order_id and instance_id are one-to-many relationships; status represents the status of the resource; opt_status represents the operational status of a resource, and because the same order may create multiple resources, theoretically resources in one order are uniformly delivered, the opt_status of all resources in the same order are uniform.
In step A3, resource-server service in the resource management layer service cluster is mainly responsible for resource management, including operations such as resource list, resource details and the like; each resource module corresponds to a resource management layer service cluster.
In step A3, a database instance table in the resource management layer service cluster is mainly used for storing the basic information of the resources corresponding to the resource modules; the id column in the Instance table is the table primary key; the instance_id column is the resource id; status represents the status of the resource.
In step A4, a schedule scheduling service in a resource management layer service cluster is mainly responsible for scheduling tasks of a resource management layer, wherein the schedule has two tasks, one of the tasks is that the schedule scheduling task sends a request to a resource module every 30 seconds, and the states of all resources in non-deletion and non-creation failure states are acquired according to the states in an instance table and a local library is updated; and secondly, when the resource is created, if the resource state is in the creation for more than 30 minutes, updating the resource state to be the creation failure.
In step A5, the schedule scheduling service in the service cluster of the operation management layer is mainly responsible for the scheduling task of the operation management layer, and the schedule scheduling service sends a request to each service cluster of the resource management layer every 30 seconds, and obtains the states of all the resources in the creation and updates the local library according to the states in the instance table; the schedule dispatch service judges whether the opt_status is all resources of the same order_id in the creation process or not according to the opt_status and order_id in the instance table every 30 seconds, updates the opt_status state if the creation is successful or not, notifies the transaction-server service to pay back if the creation is failed, and updates the opt_status to the creation failure if the creation is failed.
In step B2, after receiving the request, the resource-server service in the operation management layer service cluster directly acquires the state information from the local library and returns the state information; the returned state is determined according to status and opt_status, if opt_status is in creation, the returned state is in creation; if opt_status is running, returning to status state; if opt_status is a creation failure, then a creation failure is returned.
In step B3, the redis-server service in the operation management layer service cluster is used for caching distributed data; the record of the synchronous state in the redis cache has a life cycle of 15s, namely if the user frequently acquires the request of the resource state in 15s, the resource management layer is only needed to acquire once and update the local library, so that the response speed is improved and the concurrence is improved.
In step B4, the schedule scheduling service in the service clusters of the management layer is operated, and each resource management layer service cluster is sent to obtain the specified resource state every hour, so as to avoid the situation that the long-time resource state is inconsistent due to the fact that the user does not manually operate to obtain the instance state for a long time.
It should be noted that the following detailed description is exemplary and is intended to provide further explanation of the present application.
According to the deployment environment shown in fig. 1, at least one operation management layer service cluster and one resource management layer service cluster are deployed, and the resource management layer service cluster manages one resource module, where the resource module has the capability of separately creating resources such as computing, network, storage, and the like. At least a transaction-server service, a resource-server service, a database service, a schedule service, a redis service and the like need to be deployed in the operation management layer service cluster. At least resource-server service, database service, schedule service and the like need to be deployed in the resource management layer service cluster.
For the flow implementation of resource creation:
the user orders and creates resources, and the transmission-server service in the operation management layer service cluster receives the request; after receiving the request, the transaction-server service in the operation management layer service cluster calls the resource-server service in the operation management layer service cluster, and the resource-server service stores a database instance table and sends the request to the resource-server service in the resource management layer service cluster to request for creating resources; after receiving the request, the resource-server service in the resource management layer service cluster stores a database instance table, and sends the request to a resource module to create a resource; a schedule scheduling service in the resource management layer service cluster checks the state of the created resource to the resource module every 30 seconds and updates the local library; and (3) the schedule scheduling service in the operation management layer service cluster acquires the created resource state from the resource-server service in the resource management layer service cluster every 30 seconds, and updates the local library.
For resource status query flow implementation:
a user inquires the resource state through a UI interface or openapi, and a resource-server in the operation management layer service cluster receives a request; after receiving the request, the resource-server in the operation management layer service cluster directly acquires the state information from the local library instance table and returns the state information; after receiving the request, the resource-server in the operation management layer service cluster judges whether the redis cache has synchronous records, and if the synchronous records do not have the state of asynchronously calling the resource-server synchronous resources in the resource management layer service cluster; the life cycle of synchronous record in the redis cache is 15s; the schedule dispatch service in the operation management layer service cluster regularly calls the resource-server in the resource management layer service cluster to synchronize the states of all resources.
The above embodiments are merely preferred embodiments of the present invention and are not intended to limit the present invention, and any modifications, equivalent substitutions, improvements, etc. within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (5)
1. A method for synchronizing resource states among cloud service heterogeneous subsystems is characterized by comprising the following steps: the resource creating method comprises a resource creating method and a resource state inquiring method, wherein the resource creating method comprises the following steps of:
a1, a user orders and creates resources through a UI interface or an openapi, and a transmission-server service in an operation management layer service cluster receives a request;
a2, after receiving the request, the transaction-server service in the operation management layer service cluster calls the resource-server service in the operation management layer service cluster, and the resource-server service stores a database instance table and sends the request to the resource-server service in the resource management layer service cluster to request for creating resources;
a3, after receiving the request, the resource-server service in the resource management layer service cluster stores a database instance table, and sends the request to a resource module to create a resource;
a4, checking the state of creating the resource to a resource module every 30 seconds by using a schedule scheduling service in the resource management layer service cluster, and updating a local library;
a5, the schedule scheduling service in the operation management layer service cluster acquires the created resource state from the resource-server service in the resource management layer service cluster every 30 seconds, and updates the local library;
the resource state query method comprises the following steps:
b1, a user inquires the resource state through a UI interface or an openapi, and a resource-server in an operation management layer service cluster receives a request;
b2, after receiving the request, the resource-server in the operation management layer service cluster directly acquires the state information from the local library instance table and returns the state information;
b3, after receiving the request, judging whether the redis cache has synchronous records or not, and if the synchronous records do not have the state of asynchronously calling the resource-server synchronous resources in the resource management layer service cluster; the life cycle of synchronous record in the redis cache is 15s;
b4, scheduling service in the operation management layer service cluster regularly calls resource-server in the resource management layer service cluster to synchronize the states of all resources;
in step A2, the resource-server service in the operation management layer service cluster is used for managing resources, and comprises a resource list and resource details;
the operation management layer service cluster manages a plurality of resource management layer service clusters, and integrates resource information of users distributed in a plurality of resource modules;
in step A4, the schedule scheduling service in the resource management layer service cluster is used to send a request to the resource module every 30 seconds, and according to the states in the instance table, obtain the states of all the resources in the non-deleted and non-created failure states and update the local library;
the schedule scheduling service in the resource management layer service cluster is also used for updating the resource state to be failed in creation when the resource state is in creation for more than 30 minutes when the resource is created;
in step A2, a database instance table in the service cluster of the operation management layer is used for storing the basic information of resources of all users distributed in all resource modules;
in step A3, resource-server service in resource management layer service cluster is used for resource management, including resource list and resource detail;
each resource module corresponds to a resource management layer service cluster;
in step A3, a database instance table in the resource management layer service cluster is used for storing the resource basic information of the corresponding resource module.
2. The method for synchronizing resource states among heterogeneous subsystems of cloud services according to claim 1, wherein the method comprises the following steps: in step A1, the transaction-server service in the operation management layer service cluster is used for taking charge of operations related to user transactions, including order placing and order returning.
3. The method for synchronizing resource states among heterogeneous subsystems of cloud services according to claim 1, wherein the method comprises the following steps: in step B2, after receiving the request, the resource-server service in the operation management layer service cluster directly acquires the state information from the local library and returns the state information;
wherein the status returned is determined based on status and opt_status.
4. The method for synchronizing resource states among heterogeneous subsystems of cloud services according to claim 1, wherein the method comprises the following steps: in step B3, the redis-server service in the operation management layer service cluster is used for caching distributed data;
the record of the synchronous state in the redis cache is cached for 15s.
5. The method for synchronizing resource states among heterogeneous subsystems of cloud services according to claim 1, wherein the method comprises the following steps: in step B4, the schedule scheduling service in the service cluster of the operation management layer obtains the resource status of the service cluster of the specified resource management layer every hour, so as to avoid the situation that the long-time resource status is inconsistent due to the fact that the user does not manually operate to obtain the instance status for a long time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010192901.0A CN111431985B (en) | 2020-03-18 | 2020-03-18 | Method for synchronizing resource states among cloud service heterogeneous subsystems |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010192901.0A CN111431985B (en) | 2020-03-18 | 2020-03-18 | Method for synchronizing resource states among cloud service heterogeneous subsystems |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111431985A CN111431985A (en) | 2020-07-17 |
| CN111431985B true CN111431985B (en) | 2023-04-21 |
Family
ID=71549623
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010192901.0A Active CN111431985B (en) | 2020-03-18 | 2020-03-18 | Method for synchronizing resource states among cloud service heterogeneous subsystems |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111431985B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112422340B (en) * | 2020-11-18 | 2023-05-23 | 北京魔带互联科技有限公司 | Method for managing cloud service cluster |
| CN112600943B (en) * | 2021-03-01 | 2021-06-01 | 上海洋漪信息技术有限公司 | Message synchronization method of heterogeneous system in high-concurrency data state |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102346460A (en) * | 2011-05-27 | 2012-02-08 | 运软网络科技(上海)有限公司 | Transaction-based service control system and method |
| CN103593229A (en) * | 2013-11-26 | 2014-02-19 | 西安工程大学 | Integrating and uniform dispatching frame of heterogeneous cloud operation systems and dispatching method thereof |
| CN104536804A (en) * | 2014-12-23 | 2015-04-22 | 西安电子科技大学 | Virtual resource dispatching system for related task requests and dispatching and distributing method for related task requests |
| CN105939375A (en) * | 2016-04-13 | 2016-09-14 | 福州大学 | PaaS hybrid cloud construction method based on model |
| CN106209443A (en) * | 2016-07-01 | 2016-12-07 | 成都镜杰科技有限责任公司 | Client relation management method based on cloud computing |
| CN106534306A (en) * | 2016-11-14 | 2017-03-22 | 北京大学（天津滨海）新代信息技术研究院 | Extensible heterogeneous cloud platform adaptation method and system |
| CN107577780A (en) * | 2017-09-13 | 2018-01-12 | 郑州云海信息技术有限公司 | A kind of data center's cloud resource synchronous method and device |
| CN108282501A (en) * | 2017-01-05 | 2018-07-13 | 阿里巴巴集团控股有限公司 | A kind of Cloud Server resource information synchronous method, device and system |
| CN108701182A (en) * | 2016-08-31 | 2018-10-23 | 甲骨文国际公司 | The data management of multi-tenant identity cloud service |
| CN109067903A (en) * | 2018-08-29 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of cloud platform cascade system |
| CN109561147A (en) * | 2018-11-30 | 2019-04-02 | 武汉烽火信息集成技术有限公司 | A kind of isomery cloud management method and system, isomery cloud management system constituting method |
| CN110198231A (en) * | 2018-05-08 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Capacitor network management method and system and middleware for multi-tenant |
| CN110674153A (en) * | 2019-09-25 | 2020-01-10 | 北京金山云网络技术有限公司 | Data consistency detection method and device and electronic equipment |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018053258A1 (en) * | 2016-09-16 | 2018-03-22 | Oracle International Corporation | Tenant and service management for a multi-tenant identity and data security management cloud service |
| US10592290B2 (en) * | 2018-01-10 | 2020-03-17 | International Business Machines Corporation | Accelerating and maintaining large-scale cloud deployment |
| US10581966B2 (en) * | 2018-05-30 | 2020-03-03 | Microsoft Technology Licensing, Llc | Cloud services integrated backup and restore |
-
2020
- 2020-03-18 CN CN202010192901.0A patent/CN111431985B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102346460A (en) * | 2011-05-27 | 2012-02-08 | 运软网络科技(上海)有限公司 | Transaction-based service control system and method |
| CN103593229A (en) * | 2013-11-26 | 2014-02-19 | 西安工程大学 | Integrating and uniform dispatching frame of heterogeneous cloud operation systems and dispatching method thereof |
| CN104536804A (en) * | 2014-12-23 | 2015-04-22 | 西安电子科技大学 | Virtual resource dispatching system for related task requests and dispatching and distributing method for related task requests |
| CN105939375A (en) * | 2016-04-13 | 2016-09-14 | 福州大学 | PaaS hybrid cloud construction method based on model |
| CN106209443A (en) * | 2016-07-01 | 2016-12-07 | 成都镜杰科技有限责任公司 | Client relation management method based on cloud computing |
| CN108701182A (en) * | 2016-08-31 | 2018-10-23 | 甲骨文国际公司 | The data management of multi-tenant identity cloud service |
| CN106534306A (en) * | 2016-11-14 | 2017-03-22 | 北京大学（天津滨海）新代信息技术研究院 | Extensible heterogeneous cloud platform adaptation method and system |
| CN108282501A (en) * | 2017-01-05 | 2018-07-13 | 阿里巴巴集团控股有限公司 | A kind of Cloud Server resource information synchronous method, device and system |
| CN107577780A (en) * | 2017-09-13 | 2018-01-12 | 郑州云海信息技术有限公司 | A kind of data center's cloud resource synchronous method and device |
| CN110198231A (en) * | 2018-05-08 | 2019-09-03 | 腾讯科技（深圳）有限公司 | Capacitor network management method and system and middleware for multi-tenant |
| CN109067903A (en) * | 2018-08-29 | 2018-12-21 | 郑州云海信息技术有限公司 | A kind of cloud platform cascade system |
| CN109561147A (en) * | 2018-11-30 | 2019-04-02 | 武汉烽火信息集成技术有限公司 | A kind of isomery cloud management method and system, isomery cloud management system constituting method |
| CN110674153A (en) * | 2019-09-25 | 2020-01-10 | 北京金山云网络技术有限公司 | Data consistency detection method and device and electronic equipment |
Non-Patent Citations (4)
| Title |
|---|
| "Restlet实战（二十六）事务 (Transaction)";ajax_cn_cn;《CSDN https://blog.csdn.net/ajax_cn_cn/article/details/83436615》;20090802;第1-9页 * |
| "一个云管理平台的架构与功能设计经验谈";高效开发运维;《CSDN https://blog.csdn.net/weixin_37098404/article/details/102705737》;20170102;第1-10页 * |
| "分布式数据流计算系统的数据缓存技术综述";袁旭初等;《大数据》;20200228;第102-116页 * |
| "面向异构资源集成的数字图像实验平台";王荣等;《计算机工程与应用》;20180402;第185-191页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111431985A (en) | 2020-07-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109756366B (en) | Intelligent network SCP cloud service implementation system based on CAAS | |
| KR101863398B1 (en) | Method and system for synchronization mechanism on multi-server reservation system | |
| US8316293B2 (en) | System and method for rendering presentation pages based on locality | |
| CN102447736B (en) | Management and control method for user quota in multi-network storage system | |
| CN111431985B (en) | Method for synchronizing resource states among cloud service heterogeneous subsystems | |
| JP2009504030A (en) | Revenue management system and method | |
| CN103905537A (en) | System for managing industry real-time data storage in distributed environment | |
| US20030041125A1 (en) | Internet-deployed wireless system | |
| EP2221737B1 (en) | Caching email unique identifiers | |
| CN103023857B (en) | A kind of method and system of information resources remote deployment | |
| CN107122262A (en) | Database intelligent backup system based on agent | |
| US8332353B2 (en) | Synchronization of dissimilar databases | |
| CN101594256A (en) | Disaster recovery method, device and system | |
| CN110262807A (en) | Cluster creates Progress Log acquisition system, method and apparatus | |
| CN102333108A (en) | Distributed cache synchronization system and method | |
| US20060259523A1 (en) | System and method of synchronization of internal data cache with wireless device application data repositories | |
| CN111641521A (en) | Ambari-based method for deploying big data clusters on cloud | |
| CN114416200A (en) | System and method for monitoring, acquiring, configuring and dynamically managing and loading configuration of declarative cloud platform | |
| CN103491137A (en) | Data synchronizing system and data synchronizing method | |
| CN113992695B (en) | Method for service cooperation between network element devices and network element device | |
| CN104391876A (en) | Static data storing and querying method and system | |
| CN101547414B (en) | Short message billing system and method | |
| CN113326148A (en) | Data interaction system based on micro-service | |
| CN113127499A (en) | Block chain-based micro-service method, equipment and medium | |
| CN116260878A (en) | Service center system based on global service structure server of distributed computing and storage |
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 |