Data reconciliation method, medium, cloud platform and electronic equipment

Abstract

The invention is applied to the technical field of cloud, and provides a data reconciliation method, a medium, a cloud platform and electronic equipment, and the method comprises the steps that a business system generates metadata change information according to changed metadata, and sends the metadata change information to a reconciliation platform; and after receiving the metadata change information, the account checking platform obtains the metadata in each business system and compares the metadata in each business system. And if it is determined that the business systems retain the metadata which should be deleted or modified, or it is determined that the business systems do not add the latest metadata which needs to be added, the account checking platform notifies the business systems to update the corresponding metadata. Furthermore, real-time reconciliation can be performed according to the metadata change information, whether the metadata in each business system is consistent or not is determined, the problem that a wrong management result is generated due to the fact that the metadata which is not updated exists in the business system is avoided, and the real-time performance of data reconciliation is improved.

Description

Technical Field

[0001] This application relates to the field of cloud technology, and in particular, to a data reconciliation method, a medium, a cloud platform, and an electronic device. Background Art

[0002] With the rapid development of cloud computing technology and various network infrastructures, the traditional Internet technology (IT) business architecture is gradually using the resources provided by the cloud platform. The cloud platform provides a large number of cloud services to users, including various virtualized hardware resource instances, such as servers and memories of different specifications, and also includes software resource instances, such as cloud database instances and cloud application instances of different specifications.

[0003] In order to manage the instances on the cloud platform, the cloud platform system also includes business systems such as instance management, backup management, and metering management. Among them, each business system stores the metadata of each instance. When the metadata of an instance in a certain business system changes, if other business systems do not synchronize the changed metadata, it will cause incorrect management results in other business systems. For example, if an instance in the instance management system has been deleted, but the backup management system has not obtained the information that the instance has been deleted, it will cause the metadata of the instance to still be saved in the backup management system, and the billing platform will still generate a cost bill for the deleted instance, so that the user who once used the instance will still continue to receive billing information. Summary of the Invention

[0004] In view of this, this application provides a data reconciliation method, a medium, a cloud platform, and an electronic device.

[0005] In a first aspect, a data reconciliation method is provided, including: receiving metadata update information of a first business system in a plurality of business systems in a cloud platform, where the plurality of business systems each include a target metadata database, and the metadata update information indicates that the target metadata database of the first business system has updated first metadata; reconciling the metadata in the target metadata databases of the plurality of business systems to determine a second business system in the plurality of business systems that has not updated the first metadata in the target metadata database; and sending notification information for updating the first metadata to the second business system.

[0006] In the above solution, the method can be executed by a reconciliation platform in a cloud platform. The business system generates metadata change information based on the changed metadata and sends the metadata change information to the reconciliation platform. The reconciliation platform can be a physical server, a virtual machine, or a server cluster in the cloud platform. After receiving the metadata update information, the reconciliation platform will trigger data reconciliation to determine whether other business systems have updated the metadata. If there is a business system that has not updated the metadata, the business system will be notified to update the metadata. Furthermore, the reconciliation platform can trigger real-time reconciliation based on the metadata change information to ensure that the metadata in each business system is consistent, avoiding the problem of incorrect management results caused by the business system not updating the metadata.

[0007] In combination with the first aspect, in some implementation manners, the metadata change information includes a first range corresponding to the first metadata in the target metadata database; reconciling the metadata in the target metadata databases of multiple business systems includes: generating a first structured query statement, where the first structured query statement is used to indicate that the reconciliation range is the first range; based on the first structured query statement, reconciling the metadata in the first range in the target metadata databases of multiple business systems.

[0008] In the above solution, the metadata change information may include the range of metadata changes, such as the data table where the changed metadata is located, the data row where it is located, etc. Furthermore, according to the change event, the range where the metadata change occurs can be determined, the granularity of data reconciliation can be determined, and a structured query statement for data reconciliation can be generated, so that it is not necessary to perform row-level reconciliation every time, which can shorten the time of data reconciliation and improve the efficiency of data reconciliation.

[0009] In combination with the first aspect, in some implementation manners, the metadata change information includes metadata change events, and the metadata change events include one or more of creating an instance, deleting an instance, changing an instance, deleting a backup, modifying a backup policy, and deleting a backup policy.

[0010] In the above solution, the metadata change information can be a logical log of data changes generated by the metadata database, and the logical log is used to record the logic of the operations corresponding to the data changes, such as the structured query language corresponding to operations such as deletion and insertion.

[0011] In combination with the first aspect, in some implementation manners, based on the first structured query statement, the metadata in the first range in the target metadata databases of multiple business systems is sent to a data warehouse of the first type for reconciliation, and the data warehouse of the first type includes an online analytical processing data warehouse.

[0012] In the above solution, the first type of data warehouse can be an online big data analysis system, which can be responsible for processing reconciliation structured query statements at the second level. The online analytical processing data warehouse can specifically be a high-performance data query service, etc.

[0013] Combined with the first aspect, in some implementation manners, the multiple business systems include one or more of an instance management system, a backup management system, a resource management system, and a metering management system.

[0014] In the above solution, the resource management system is used to manage resources such as computing resources, storage resources, or application programs. The instance management system is used to manage each instance generated based on the resources. The backup management system is used to back up the data of each instance. The metering management system is used to manage, monitor, and statistically analyze the data of other business systems.

[0015] In a second aspect, a data reconciliation method is provided, which is applied to a cloud platform. The cloud platform includes multiple business systems and a reconciliation platform. Among them, the multiple business systems all include a target metadata database. The method includes: the first business system among the multiple business systems sends metadata update information to the reconciliation platform, and the metadata update information indicates that the target metadata database of the first business system has updated the first metadata; the reconciliation platform reconciles the metadata in the target metadata databases of the multiple business systems, and determines a second business system among the multiple business systems that has not updated the first metadata; the reconciliation platform sends a notification message for updating the first metadata to the second business system.

[0016] In the above solution, the method can be executed by the reconciliation platform in the cloud platform. The business system generates metadata change information according to the changed metadata and sends the metadata change information to the reconciliation platform. The reconciliation platform can be a physical server, a virtual machine, or a server cluster in the cloud platform. After receiving the metadata update information, the reconciliation platform will trigger data reconciliation to determine whether other business systems update the metadata. If there is a business system that has not updated the metadata, it will notify the business system to update the metadata. Furthermore, the reconciliation platform can trigger real-time reconciliation according to the metadata change information to ensure that the metadata in each business system is consistent, avoiding the problem of incorrect management results caused by the business system not updating the metadata.

[0017] In combination with the second aspect, in some implementation manners, the cloud platform further includes a data processing platform. The first business system among multiple business systems sends metadata update information to the reconciliation platform, including: the first business system among multiple business systems sends metadata update information to the data processing platform; the data processing platform determines a first range corresponding to the first metadata in the target metadata database according to the metadata update information; the data processing platform sends the first range to the reconciliation platform; and the reconciliation platform reconciles the metadata in the target metadata databases of multiple business systems, including: the reconciliation platform generates a first structured query statement, and the first structured query statement is used to indicate that the reconciliation range is the first range; the reconciliation platform reconciles the metadata in the first range in the target metadata databases of multiple business systems based on the first structured query statement.

[0018] In the above solution, the data processing system can be used to extract the range of metadata changes in the metadata change information, such as the data table where the changed metadata is located, the data row where it is located, etc. Furthermore, according to the change event, the range where the metadata change is located can be determined, the granularity of data reconciliation can be determined, and a structured query statement for data reconciliation can be generated, so that it is not necessary to perform row-level reconciliation every time, which can shorten the time of data reconciliation and improve the efficiency of data reconciliation.

[0019] In combination with the second aspect, in some implementation manners, the data processing platform includes a data replication service, a streaming media platform, and a stream processing platform. The first business system among multiple business systems sends metadata update information to the reconciliation platform, including: the first business system among multiple business systems sends metadata update information to the data replication service; the data replication service sends the metadata update information to the stream processing platform through the streaming media platform; the stream processing platform determines a first range corresponding to the first metadata in the target metadata database according to the metadata update information; the stream processing platform sends the first range to the reconciliation platform.

[0020] In the above solution, a data replication service, a streaming media platform, and a stream processing platform are adopted to distribute and process the metadata change information. When the metadata of the business system changes frequently, a large amount of metadata change information will be generated. Using this data processing platform, a large amount of metadata change information can be processed and sent to the reconciliation platform, and then the reconciliation platform can generate reconciliation statements in a timely manner, so that data reconciliation can be completed in a timely manner.

[0021] In a third aspect, the present application provides a cloud platform, which includes multiple business systems and a reconciliation platform. Among them, each of the multiple business systems includes a target metadata database. The first business system among the multiple business systems is configured to send metadata update information to the reconciliation platform, where the metadata update information indicates that the target metadata database of the first business system has updated the first metadata; the reconciliation platform is configured to reconcile the metadata in the target metadata databases of the multiple business systems to determine a second business system among the multiple business systems that has not updated the first metadata; the reconciliation platform is further configured to send notification information for updating the first metadata to the second business system.

[0022] In a fourth aspect, the present application provides an electronic device, including a processor and a memory. The memory is used to store instructions, and the processor is used to execute the instructions. When the processor executes the instructions, the method described in the first aspect is performed.

[0023] In a fifth aspect, the present application provides a computer-readable storage medium, in which instructions are stored. When the instructions run on an electronic device, the method described in the first aspect is performed.

[0024] In a sixth aspect, the present application provides a computer program product, which includes computer instructions. When executed by a computing device, the computing device performs the method described in the first aspect. Description of the Drawings

[0025] To more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for the description of the embodiments.

[0026] Figure 1 It is a schematic diagram of an application scenario of a cloud platform provided by an embodiment of the present application;

[0027] Figure 2 It is a schematic diagram of the structure of a cloud platform provided by an embodiment of the present application;

[0028] Figure 3 It is a schematic diagram of the flow of a data reconciliation method provided by an embodiment of the present application;

[0029] Figure 4 It is a schematic diagram of the structure of the first data reconciliation system provided by an embodiment of the present application;

[0030] Figure 5 It is a schematic diagram of the structure of the second data reconciliation system provided by an embodiment of the present application;

[0031] Figure 6 It is a schematic diagram of the structure of the third data reconciliation system provided by an embodiment of the present application;

[0032] Figure 7It is a schematic structural diagram of a data reconciliation device provided by an embodiment of the present application;

[0033] Figure 8 It is a schematic structural diagram of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0034] Illustrative embodiments of the present application include, but are not limited to, data reconciliation methods, media, cloud platforms, and electronic devices.

[0035] First, the cloud platform system involved in some embodiments of the present application will be introduced.

[0036] Cloud service providers connect a large number of resources through a network to form a cloud platform, and uniformly manage, allocate, and schedule the cloud platform to provide cloud services to users. The cloud platform includes different cloud service instances such as computing resources, storage resources, or application programs. The cloud service instance essentially means virtualizing various resources on the cloud platform into containers or virtual machines. As Figure 1 shown, users can obtain these containers or virtual machines on the cloud platform 20 through the network, and then use the corresponding computing resources, storage resources, or application program functions on the terminal 10.

[0037] The above terminal 10 may be a terminal device such as a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, etc.

[0038] Specifically, cloud services include multiple service models, including infrastructure as a service (IaaS), platform as a service (PaaS), and software as a service (SaaS).

[0039] IaaS provides users with basic hardware resource services, such as at least one of hardware facilities such as servers, central processing units (CPUs), storage media, computer networks, and routers. For example, elastic compute service (ECS), elastic volume service (EVS), object storage service (OBS), virtual private cloud (VPC), elastic load balance (ELB).

[0040] On top of the hardware resource services provided by IaaS, PaaS also provides software resource services such as operating systems, dependent libraries, and databases to users. That is, a software environment for building application programs is also provided in the cloud host.

[0041] On top of IaaS and PaaS, SaaS directly provides runnable application programs, namely cloud applications. Users can run the application programs by downloading the micro - clients corresponding to the cloud applications, without the need for users to download the application programs to local devices. Here, the micro - client refers to a micro - client or a thin client.

[0042] The cloud platform 20 also provides a business system for managing cloud service instances. In each business system in the cloud platform 20, metadata related to the instances is stored. The metadata can be stored in the database of the business system, hereinafter referred to as the metadata database. The metadata may include the name, version, corresponding user identifier, etc. of the instance. Exemplarily, when the instance is a cloud database, the metadata of the cloud database instance may include the name, version number, whether read operations are supported, the name of the required driver, etc.

[0043] For example, Figure 2 shows a schematic architecture diagram of a cloud platform 20. As Figure 2 shown, the architecture includes multiple business systems. For example, a resource management system 21, an instance management system 22, a backup management system 23, a metering management system 24, and a billing platform 25. The above - mentioned business systems are used to manage multiple instances on the cloud platform 20 and have the same metadata database, which contains the metadata of each instance.

[0044] Among them, the resource management system 21 is used to manage resources such as computing resources, storage resources, or application programs included in the above - mentioned IaaS, PaaS, and SaaS. The instance management system 22 is used to manage each instance generated based on the resources, including managing the user accounts corresponding to the instances. The backup management system 23 is used to back up the data of each instance. The metering management system 24 is connected to the resource management system 21, the instance management system 22, and the backup management system 23, and is used to manage, monitor, and statistically analyze the data of the above - mentioned systems, and send the data to the billing platform 25, and the billing platform 25 generates the bills for the instances used by users.

[0045] The above-mentioned resource management system 21, instance management system 22, backup management system 23, metering management system 24, and billing platform 25 can be general physical servers. For example, ARM servers or X86 servers. The above systems can also be virtual machines (VMs) implemented by network functions virtualization (NFV) technology. A virtual machine refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment. The above systems can also be a server cluster. Among them, each server in the server cluster can be implemented by the above physical server or the above virtual machine.

[0046] It should be noted that Figure 2 This is just a possible implementation manner of the embodiments of the present application. In practical applications, the cloud platform 20 may also include more or fewer business systems, which are not limited here.

[0047] The process of generating call detail records (CDRs) by the cloud platform 20 will be described by way of example below. For example, a user purchases instance A on the cloud platform 20. The instance management system 22 stores the usage data and metadata of instance A. The resource management system 21 is used to manage the hardware resources and / or software resources used by instance A and also stores the metadata of instance A. To prevent data loss of instance A, the user can back up the data of instance A, or the cloud platform 20 can automatically back up instance A. As a result, the backup management system 23 also stores the backup data and metadata of instance A.

[0048] The metering management system 24 will regularly monitor the relevant data of instance A in the resource management system 21, instance management system 22, and backup management system 23. Or when the instance management system 22 obtains the situation that the user stops using instance A, the metering management system 24 will also obtain the relevant data of instance A in each business system.

[0049] The metering management system 24 will count the data of instance A in each business system. For example, the usage duration of instance A in the instance management system 22, the specifications of the resources used by instance A in the resource management system 21, the data backup duration and the amount of data backed up of instance A in the backup management system 23, etc. Then, the metering management system 24 sends the counted data of instance A to the billing platform 25, and the billing platform 25 will generate the call detail record corresponding to instance A according to the above statistical data. That is to say, the call detail record for the user to pay for instance A is obtained by integrating the data reported by each business system.

[0050] After the instance management system 22 obtains that the user has stopped using instance A and after each business system reports the relevant data of instance A, the instance management system 22 will also notify the backup management system 23 to delete the backup data and metadata of instance A, and notify the resource management system 21 to release the hardware resources and / or software resources occupied by instance A and delete the metadata of instance A.

[0051] When the metadata in a certain business system changes, if the business system does not send the changed metadata to other business systems, or due to network problems, other business systems do not receive the changed metadata, it will cause other business systems to still manage the instance according to the unupdated metadata.

[0052] For example, after a certain instance in the instance management system 22 has been deleted, due to network anomalies and other problems, both the backup management system 23 and the resource management system 21 do not obtain the information that the instance has been deleted. And since the metering management system 24 counts the instance data based on all business systems, the backup management system 23 will still report the data of the deleted instance to the metering management system 24, such as the data volume of the backed-up instance, causing the billing platform 25 to still generate the call records generated by the instance in the backup management system 23, resulting in abnormal user payments. It will also cause the resource management system 21 not to release the IaaS resources corresponding to the deleted instance. For example, the ECS and EVS corresponding to the instance still store the data corresponding to the instance, causing the IaaS resources to be occupied and unable to be put into use for other instances.

[0053] To solve the problem of unsynchronized metadata between business systems, the present application provides a data reconciliation method, including: the business system will generate metadata change information according to the changed metadata and send the metadata change information to the reconciliation platform. After receiving the metadata change information, the reconciliation platform will obtain the metadata in each business system and compare the metadata in each business system (i.e., data reconciliation). Then, the reconciliation platform can perform real-time reconciliation according to the metadata change information to determine whether the metadata in each business system is consistent. For example, if it is determined that there is a business system that retains metadata that should be deleted or modified, or it is determined that there is a business system that does not add the latest metadata that needs to be added, the reconciliation platform will notify these business systems to update the corresponding metadata, such as notifying the business system to obtain the latest metadata from the business system with the latest metadata.

[0054] Furthermore, the reconciliation platform can trigger real-time reconciliation according to the metadata change information to ensure that the metadata in each business system is consistent, avoiding the problem of incorrect management results caused by business systems not updating metadata.

[0055] In some embodiments, the reconciliation platform may be a physical server, a virtual machine, or a server cluster in the cloud platform 20 that communicates with business systems such as the instance management system 22 or control platforms such as the billing platform 25, or it may be software on the above devices.

[0056] In some embodiments, the metadata change information may be an identifier indicating that the metadata has changed. Specifically, the metadata change information may also be a logical log, and the logical log may specifically record the metadata change events. The change events may specifically be metadata change events such as creating an instance, deleting an instance, changing an instance, deleting a backup, modifying a backup policy, and deleting a backup policy. When the reconciliation platform performs data reconciliation, it may perform database-level, table-level, or row-level reconciliation on the metadata database according to the scope of the metadata modified corresponding to the change event. For example, if the change event indicates that a data table corresponding to a certain instance has been deleted, then the reconciliation platform may perform reconciliation on the metadata databases of each business system at the table level to determine whether the data table has been deleted in other business systems.

[0057] Furthermore, the reconciliation platform can perform real-time reconciliation based on the metadata change information to determine whether the metadata in each business system is consistent. Moreover, it can also determine the granularity of data reconciliation according to the type of change event recorded in the metadata change information. Thus, it is not necessary to perform row-level reconciliation every time, which can shorten the time of data reconciliation and improve the efficiency of data reconciliation.

[0058] In other embodiments, when the reconciliation platform performs data reconciliation, it may first import the metadata in each business system into a data warehouse with a larger storage space, and then the reconciliation platform compares the metadata of each business system in the data warehouse. If the comparison result indicates that there is unupdated metadata (also known as dirty data) in the business system, the business system will be notified to update the metadata. For example, delete the dirty data, replace the dirty data with the latest metadata, or add the newly added metadata. Furthermore, the reconciliation platform can perform real-time reconciliation based on the metadata change information to ensure that the metadata in each business system is consistent, avoiding the problem of incorrect management results caused by unupdated metadata in the business system.

[0059] In other embodiments, the reconciliation platform can not only perform real-time reconciliation based on the metadata change information but also perform reconciliation on the business system regularly at a preset time. For example, the reconciliation platform can perform real-time reconciliation according to the metadata change information and also import the metadata in each business system into the data warehouse at a fixed time every day, and then the reconciliation platform performs reconciliation. Thus, it can avoid the problem that the metadata change information fails to be sent due to network failures or other problems, resulting in the reconciliation platform not being able to perform data reconciliation in a timely manner.

[0060] In summary, the data reconciliation method provided by this application can perform real-time reconciliation based on metadata change information, determine whether the metadata in each business system is consistent, avoid the problem of incorrect management results caused by unupdated metadata in the business system, and improve the real-time performance of data reconciliation. Moreover, the data reconciliation method can also determine the magnitude of data reconciliation according to the change event type recorded in the metadata change information, thereby shortening the time for data reconciliation and improving the efficiency of data reconciliation. The data reconciliation method can also reconcile data at a preset time, thereby improving the reliability of data reconciliation.

[0061] Next, the data reconciliation method provided by the embodiments of this application will be introduced. This data reconciliation method is applied to the reconciliation platform in the above cloud platform. The cloud platform includes multiple business systems, and the multiple business systems include a first business system and a second business system. As Figure 3 shown, this method specifically includes:

[0062] S310: Receive the metadata update information of the first business system.

[0063] Each of the multiple business systems includes a metadata database of instances. When the metadata in the metadata database of a business system changes, metadata change information will be sent to the reconciliation platform.

[0064] The metadata change information may include an identifier indicating that the metadata has changed, and may also include a change event. The change event may specifically be a metadata change event such as creating an instance, deleting an instance, changing an instance, deleting a backup, modifying a backup policy, deleting a backup policy, etc. For example, creating an instance may be that a user newly purchases a certain instance, and then the metadata databases of each business system need to add the metadata of this instance. Deleting an instance may be that a user stops using a certain instance, and then the metadata databases of each business system need to delete the metadata of this instance. Changing an instance may refer to changing the user information, hardware resource specifications, etc. of the instance, and then the metadata databases of each business system need to modify the information corresponding to the changed instance. Deleting a backup may be to delete the backup data of a certain instance in the backup management system 23, and then the metadata databases of each business system need to modify the backup information such as whether to back up for this instance. Moreover, deleting a backup may be synchronously performed after deleting an instance, or may be to only delete the backup of this instance in the backup management system 23 when the instance is not deleted and the instance is still in use. Modifying a backup policy may be to modify the automatic backup period, backup data range, etc. of a certain instance, and then the metadata databases of each business system need to modify the backup policy corresponding to the changed instance. Deleting a backup policy may be that a user deletes the subsequent backup policy for this instance, but does not delete the data that has been backed up for this instance in the backup management system 23. Then the metadata databases of each business system need to modify the recorded backup policy for this instance.

[0065] It should be understood that the above only gives examples of change events. In actual applications, the metadata change information may also include other change events, and the present application does not make specific limitations thereon.

[0066] In some embodiments, the change event can also reflect the scope of metadata changes, such as the data table where the changed metadata is located, the data row where it is located, etc.

[0067] In other embodiments, the metadata change information can be the logical log of data changes generated by the metadata database, or it can also be a physical log. Among them, the logical log is used to record the logic of the operations corresponding to data changes, such as the structured query language (SQL) corresponding to operations such as delete, insert, etc. The physical log is used to record the specific content of data changes, such as the modified content on a certain data page.

[0068] In other embodiments, taking Figure 2 the architecture of the cloud platform 20 shown as an example, the reconciliation platform can directly establish connections with multiple business systems, and the business systems directly send metadata update information to the reconciliation platform. The reconciliation platform can also be connected to the management and control platform of the business system, and the management and control platform can be the aforementioned metering management system 24 or the billing platform 25. The business system sends metadata update information to the management and control platform, and the management and control platform then sends the metadata update information to the reconciliation platform.

[0069] In other embodiments, there is also a data processing platform between the business system or the management and control platform and the reconciliation platform. The data processing platform can process the metadata change information and extract the metadata change information required by the reconciliation platform. For example, the data processing platform extracts the metadata change scope according to the logical log. For details, reference can also be made to the following Figure 4 and its related descriptions.

[0070] In other embodiments, the data processing platform can specifically be composed of one or more platforms among a data replication service (DRS) system, a Kafka distributed streaming platform (Kafka), and a streaming data processing platform. The DRS system is used to synchronously publish the metadata change information to the Kafka message queue. Kafka is a message middleware service used to build a real-time data pipeline. The streaming data processing platform can provide millisecond-level real-time data analysis between end to end.

[0071] S320: Reconcile the metadata databases of multiple business systems to determine a second business system with unupdated metadata among the multiple business systems.

[0072] Based on the received metadata update information, the reconciliation platform will reconcile the metadata databases of each business system to determine whether each business system updates the metadata corresponding to the metadata update information. If the comparison result indicates that there is unupdated metadata in the second business system among multiple business systems, step S330 will be executed. If the comparison result indicates that the metadata of each business system is the latest, the method will end.

[0073] In some embodiments, for the data reconciliation by the reconciliation platform, it can first import the metadata in each business system into a data warehouse with a large storage space, and then the reconciliation platform compares the metadata of each business system in the data warehouse.

[0074] In other embodiments, the reconciliation platform can also notify other business systems except the first business system to perform reconciliation by themselves. For example, the reconciliation platform sends the metadata update information to the second business system, and the second business system verifies whether its own metadata database updates the data based on this update information.

[0075] In other embodiments, when the data change information contains a change event, the reconciliation platform can reconcile the metadata database at the database level, table level, or row level according to the range of the metadata modified corresponding to the change event. For example, if the change event indicates that a data table corresponding to a certain instance is deleted, then the reconciliation platform can reconcile the metadata databases of each business system at the table level to determine whether the data table is deleted in other business systems. If the change event indicates that the metadata of a certain row is changed, then the reconciliation platform can only obtain the metadata of this row in each business system, reconcile the metadata of this row, and determine whether the data of this row in other business systems is changed to the latest content.

[0076] In other embodiments, specifically, the reconciliation platform can generate a reconciliation SQL statement according to the granularity of data reconciliation (such as database level, table level, or row level), and send the reconciliation SQL to the data warehouse, and the data warehouse executes the data reconciliation SQL statement. Or, the reconciliation platform sends the reconciliation SQL to the second business system, and the second business system executes the data reconciliation SQL statement.

[0077] S330: Send a notification message for updating metadata to the second business system.

[0078] Based on the comparison result indicating that there is unupdated metadata in the second business system among multiple business systems, the reconciliation platform will notify the second business system to update the metadata. For example, delete the dirty data, replace the dirty data with the latest metadata, or add the newly added metadata. The second business system can obtain the latest metadata from the first business system, or the reconciliation platform can send the metadata update information to the second business system, and the second business system updates to obtain the latest metadata according to the metadata update information.

[0079] In some embodiments, if the second business system performs data reconciliation by itself, after the second business system determines that there is unupdated metadata, the second business system can also directly obtain the latest metadata from the first business system.

[0080] In other embodiments, the reconciliation platform can perform real-time reconciliation based on metadata change information, and can also reconcile the business systems regularly at preset times. For example, the reconciliation platform can perform real-time reconciliation based on metadata change information, and can also import the metadata in each business system into the data warehouse at a fixed time every day, and then the reconciliation platform performs reconciliation. Furthermore, it is possible to avoid problems such as data reconciliation not being performed in a timely manner by the reconciliation platform due to network failures or other issues that cause the metadata change information to fail to be sent.

[0081] In summary, the data reconciliation method provided in this application can perform real-time reconciliation based on metadata change information, determine whether the metadata in each business system is consistent, avoid the problem of incorrect management results caused by unupdated metadata in the business system, and improve the timeliness of data reconciliation. Moreover, the data reconciliation system can also determine the granularity of data reconciliation according to the metadata change event of the metadata change information, thereby shortening the time of data reconciliation and improving the efficiency of data reconciliation. The data reconciliation method can also reconcile the data at preset times, thereby improving the reliability of data reconciliation.

[0082] Next, a data reconciliation system applying the above data reconciliation method will be illustrated by way of example. As Figure 4 shown, a schematic structural diagram of a data reconciliation system 40 is shown. The data reconciliation system includes a service management system 41, a data processing platform 42, and a reconciliation platform 43. Among them, the data processing platform can be a physical server, a VM, or a server cluster. And, taking the metadata change information as a logical log as an example for illustration.

[0083] The service management system 41 includes multiple business systems in the cloud platform 20, such as the resource management system 21, the instance management system 22, the backup management system 23, and the metering management system 24 shown above. The service management system 41 is used to manage the resources and / or instances in the cloud platform 20, and provide various cloud service instances to users. For specific references, please refer to the relevant descriptions above. Figure 2 shown. Figure 2 of the relevant description.

[0084] The business management system 41 includes a metadata database for each instance. When the metadata recorded in the metadata database changes, the business management system 41 will generate a logical log. The logical log is used to indicate that the metadata in the business system has changed, and the specific change events of the metadata can also be recorded in the logical log. The business management system 41 can send the logical log to the reconciliation platform 43 through the data processing platform 42.

[0085] The data processing platform 42 can be used to receive the logical log sent by the business system and send the logical log to the reconciliation platform 43, and then the reconciliation platform 43 triggers the reconciliation of the metadata databases of each business system in the business management system 41.

[0086] The data processing platform 42 can also process the logical log to extract the metadata change information required by the reconciliation platform 43. For example, the data processing platform 42 extracts the metadata change range from the logical log, such as the data table and data row corresponding to the metadata change. Or the data processing platform 42 extracts information such as the business system where the metadata change occurs from the logical log. If the change event is creating an instance, deleting an instance, changing an instance, etc., the business system where the metadata change occurs first is the instance management system 22. If the change event is deleting a backup, modifying a backup policy, deleting a backup policy, etc., the business system where the metadata change occurs first is the backup management system 23.

[0087] The reconciliation platform 43 can subscribe to the logical log of the business management system 41. That is to say, after the business management system 41 generates a logical log, it will automatically send the logical log to the data processing platform 42, and the data processing platform 42 forwards the logical log to the reconciliation platform 43. After receiving the logical log, the reconciliation platform 43 will trigger the data reconciliation of each business system in the business management system 41. Specifically, the reconciliation platform 43 can generate an SQL statement for data reconciliation according to the obtained logical log. This SQL statement will trigger the acquisition of the metadata of each business system from the business management system 41, and then the reconciliation platform 43 reconciles the obtained metadata.

[0088] The reconciliation platform 43 can also determine the metadata range that needs to be reconciled according to the metadata change information extracted by the data processing platform 42 based on the logical log. For example, the metadata range can be one or more data rows, one or more data tables, or one or more databases. Furthermore, the reconciliation platform 43 only needs to obtain the metadata corresponding to the metadata range in each business system and perform reconciliation at the corresponding data row level, data table level, or database level according to the obtained metadata.

[0089] For example, if the metadata change information indicates that a row of data in a data table in the metadata database has changed, the reconciliation platform 43 only needs to compare the row of data in this data table corresponding to each business system. Similarly, if the metadata change information indicates that a data table is added to the metadata database, the reconciliation platform 43 only needs to perform table-level reconciliation on each business system to determine whether the data table is added to other business systems.

[0090] The reconciliation platform 43 can obtain metadata through the data processing platform 42, and the data processing platform 42 can also process the obtained metadata. For example, perform format conversion on different metadata to obtain metadata in a unified format; or, filter and screen the metadata according to the change events recorded in the logical log to obtain the data rows, data tables or databases where the changed metadata is recorded.

[0091] In some other embodiments, the reconciliation platform 43 can also perform data reconciliation on the business management system 41 regularly at a preset time. For example, the preset time can be every hour or every day. For example, the regular data reconciliation can be to perform data reconciliation on all the metadata in the metadata database of each business system, and perform data reconciliation at all levels including the database level, table level or row level.

[0092] In some other embodiments, the reconciliation platform 43 can also generate reconciliation SQL statements according to the magnitude of data reconciliation (such as database level, table level or row level) and according to the time of data reconciliation (such as second level, hour level or day level), where the data reconciliation at the second level can be the data reconciliation triggered by the foregoing logical log. Furthermore, the reconciliation platform 43 can perform data reconciliation with different granularities on the metadata of each business system according to the SQL.

[0093] After the reconciliation platform 43 determines that a certain business system has not updated the latest metadata, the reconciliation platform 43 will also notify the business system to update the metadata. For example, notify the business system to obtain the latest metadata from other business systems storing the latest metadata, or the reconciliation platform 43 directly sends the latest metadata to the business system that has not updated the latest metadata.

[0094] It should be understood that Figure 4 the example is described with the business management system 41 communicating with the reconciliation platform 43 through the data processing platform 42, that is to say, the data processing platform 42 can exist independently of the reconciliation platform 43.

[0095] In some embodiments, the business management system 41 can also be directly connected to the reconciliation platform 43, and the business management system 41 can directly communicate with the reconciliation platform 43. For example, the reconciliation platform 43 can be directly connected to, such as Figure 2Control platforms such as the measurement management system 24 or the billing platform 25 shown in the figure, or are respectively connected to business systems such as the resource management system 21, the instance management system 22, the backup management system 23, and the measurement management system 24. In this case, the data processing platform 42 can also be a part of the reconciliation platform 43.

[0096] Specifically, when the metadata in the business management system 41 changes, a logical log will be sent to the reconciliation platform 43, and the reconciliation platform 43 will obtain the metadata of each business system in the business management system 41. Then, the reconciliation platform 43 can perform processing such as format conversion or filtering on the metadata, and then reconcile the metadata of each business system after processing. After the reconciliation platform 43 determines that there is a situation where the metadata of a certain business system has not been updated, the reconciliation platform 43 will also notify the business system storing the unupdated metadata to update the metadata. For specific content, reference can also be made to the relevant description above. Figure 4 and will not be elaborated here.

[0097] In summary, the data reconciliation system provided by this application can perform real-time reconciliation based on logical logs, determine whether the metadata in each business system is consistent, avoid the problem of incorrect management results caused by unupdated metadata in the business system, and improve the real-time performance of data reconciliation. Moreover, the data reconciliation system can also determine the granularity of data reconciliation according to the type of metadata change recorded in the logical log, thereby shortening the time of data reconciliation and improving the efficiency of data reconciliation. The data reconciliation method can also reconcile data at a preset time, thereby improving the reliability of data reconciliation.

[0098] In some embodiments, the structure of the data reconciliation system can also be referred to as shown in Figure 5 the figure. In the data reconciliation system 50, for example, the business system includes business system A and business system B. The database storing the metadata of business system A is denoted as metadata database A1, and the database storing the metadata of business system B is denoted as metadata database B1. It should be understood that there can also be other business systems in the data reconciliation system, and this application does not make any limitations in this regard. The data reconciliation system 50 also includes a DRS system 51, kafka 52, a stream data processing platform 53, and a data reconciliation platform 54.

[0099] When the metadata of business system A and / or business system B changes, the business system where the data change occurs will send metadata change information (such as a logical log) to the DRS system 51. The DRS system 51 will synchronously publish the received metadata change information to the kafka message queue, where kafka is a message middleware service used to build a real-time data pipeline.

[0100] Kafka 52 sends the obtained metadata change information to the streaming data processing platform 53, which can be used to process the metadata change information. For example, the metadata change scope, the specific content of newly added or deleted metadata, and the business system where the metadata change occurs can be extracted, and then the formatted data corresponding to each metadata change information can be obtained based on the above information. Among them, the streaming data processing platform 53 can provide millisecond-level real-time data analysis between end-to-end. The specific content of the streaming data processing platform 53 can also refer to the relevant description in the foregoing Figure 4 related description.

[0101] The data reconciliation platform 54 generates a reconciliation SQL statement based on the already processed and cleaned formatted data. This SQL statement includes the metadata scope that needs to be reconciled. Furthermore, the corresponding metadata in the business system can be obtained according to this SQL statement, and data reconciliation at the database level, table level, or row level can be performed according to the corresponding metadata scope to determine whether the corresponding metadata scope has been updated in each business system. The specific content of the data reconciliation platform 54 can also refer to the relevant description in the foregoing Figure 4 related description.

[0102] It should be understood that when the metadata of the business system changes frequently, a large amount of metadata change information will be generated. Through the data reconciliation system 50 as shown in Figure 5 , a large amount of metadata change information can be processed and sent to the data reconciliation platform 54. Furthermore, the data reconciliation platform 54 can generate a reconciliation SQL statement in a timely manner, enabling data reconciliation to be completed in a timely manner.

[0103] In some other embodiments, the implementation process of the data reconciliation system 50 can also refer to Figure 6 . As shown in Figure 6 , taking the control platform of the data reconciliation platform 54 connecting to the business system as an example, the control platform of the business system can be the aforementioned measurement management system 24 or the billing platform 25.

[0104] When the control platform detects that the metadata of a certain business system has changed, it will send the corresponding metadata change information to the data reconciliation platform 54. Among them, between the control platform and the data reconciliation platform 54, there may also be the DRS system 51, Kafka 52, and the streaming data processing platform 53, etc. described above, which will not be elaborated here. Figure 5

[0105] ​After the data processing platform 54 receives the metadata change information, it will perform a rule engine status poll. That is to say, it will determine whether the rules are satisfied according to the metadata change information, and then generate a reconciliation SQL. Among them, the rule engine includes rule engine 1 and rule engine 2. Rule engine 1 is used to determine whether to perform incremental reconciliation at the library level, or perform incremental reconciliation at the row level for each business system according to the scope of metadata change in the metadata change information. Rule engine 2 is used to determine the time level of data reconciliation. If the data reconciliation platform 54 performs data reconciliation according to the metadata change information, it belongs to second-level reconciliation, and only the metadata corresponding to the scope of data change needs to be reconciled. If the data reconciliation platform 54 presets regular data reconciliation, the time granularity of data reconciliation is determined according to the preset time to determine whether it is hour-level reconciliation or day-level reconciliation. If the data reconciliation platform 54 presets to perform reconciliation every hour, rule engine 2 determines that the current reconciliation belongs to hour-level reconciliation.

[0106] The data processing platform 54 can notify the corresponding data warehouse to perform data reconciliation according to the reconciliation SQL statement. The data warehouse will obtain the metadata of the metadata database of the business system, and then compare the metadata of each business system. For example, the data warehouse can include an on-line analytical processing (OLAP) data warehouse and an off-line data lake data warehouse. Among them, the OLAP data warehouse is an online big data analysis system and can be responsible for processing second-level reconciliation SQL statements. The OLAP data warehouse can specifically be a Greenplum data warehouse, a high-performance analytic appliance (HANA), a Presto data query engine, etc. The off-line data lake data warehouse is an off-line big data analysis system and can be responsible for processing hour-level or day-level and other T+1 reconciliation SQL statements. The off-line data lake data warehouse can specifically be a data lake insight (DLI), a Hive data warehouse platform, a Spark data warehouse platform, etc.

[0107] In summary, the data reconciliation system provided by this application can perform real-time processing on a large amount of metadata change information. Furthermore, the reconciliation platform can perform real-time reconciliation according to the logical log to determine whether the metadata in each business system is consistent, avoiding the problem of incorrect management results caused by unupdated metadata in the business system, and improving the real-time performance of data reconciliation. Moreover, the data reconciliation system can also determine the granularity of data reconciliation according to the type of metadata change recorded in the logical log, thereby shortening the time of data reconciliation and improving the efficiency of data reconciliation. The data reconciliation method can also reconcile data according to the preset time, thereby improving the reliability of data reconciliation.

[0108] To solve the problem of unsynchronized metadata between various business systems, the present application provides a data reconciliation device. As Figure 7 shown, the data reconciliation device 700 includes a receiving unit 710, a determining unit 720, a sending unit 730, and a generating unit 740.

[0109] The receiving unit 710 is configured to receive metadata update information of a first business system among multiple business systems in a cloud platform. Among them, multiple business systems all include a target metadata database, and the metadata update information indicates that the target metadata database of the first business system has updated the first metadata. The determining unit 720 is configured to reconcile the metadata in the target metadata databases of multiple business systems and determine a second business system among multiple business systems that has not updated the first metadata in the target metadata database. The sending unit 730 is configured to send notification information for updating the first metadata to the second business system.

[0110] In some embodiments, the metadata change information includes a first range corresponding to the first metadata in the target metadata database. The generating unit 740 is configured to generate a first structured query statement, and the first structured query statement is used to indicate that the reconciliation range is the first range. The determining unit 720 is further configured to reconcile the metadata in the first range in the target metadata databases of multiple business systems based on the first structured query statement.

[0111] In other embodiments, the metadata change information includes a metadata change event, and the metadata change event includes one or more of creating an instance, deleting an instance, changing an instance, deleting a backup, modifying a backup policy, and deleting a backup policy.

[0112] In other embodiments, the receiving unit 710 is further configured to receive the first structured query statement, and the sending unit 730 is further configured to send the metadata in the first range in the target metadata databases of multiple business systems to a data warehouse of a first type for reconciliation. The data warehouse of the first type includes an online analytical processing data warehouse.

[0113] In other embodiments, the multiple business systems include one or more of an instance management system, a backup management system, a resource management system, and a metering management system.

[0114] In summary, the data reconciliation device provided by this application can process a large amount of metadata change information in real time. Furthermore, the reconciliation platform can perform real-time reconciliation based on the logical logs to determine whether the metadata in each business system is consistent, avoiding the problem of incorrect management results caused by unupdated metadata in the business system and improving the real-time performance of data reconciliation. Moreover, the data reconciliation system can also determine the granularity of data reconciliation according to the metadata change types recorded in the logical logs, thereby shortening the time for data reconciliation and improving the efficiency of data reconciliation. The data reconciliation method can also reconcile data at a preset time, further improving the reliability of data reconciliation.

[0115] The method of the embodiment of this application is described in detail above. To facilitate better implementation of the above solution of the embodiment of this application, correspondingly, relevant devices for cooperating with the implementation of the above solution are also provided below.

[0116] Figure 8 FIG. is a schematic structural diagram of an electronic device 800 provided by this application. The electronic device 800 may be the reconciliation platform 43 or the data reconciliation platform 54 in the foregoing content. As Figure 8 shown, the electronic device 800 includes: a processor 810, a communication interface 820, and a memory 830. Among them, the processor 810, the communication interface 820, and the memory 830 may be interconnected through an internal bus 840, or may communicate through other means such as wireless transmission. In the embodiment of this application, taking the connection through the bus 840 as an example, the bus 840 may be a Peripheral Component Interconnect Express (PCIe) bus, an Extended Industry Standard Architecture (EISA) bus, a Unified Bus (Ubus or UB), a Compute Express Link (CXL), a Cache Coherent Interconnect for Accelerators (CCIX), etc. The bus 840 may be divided into an address bus, a data bus, a control bus, etc. In addition to the data bus, the bus 840 may also include a power bus, a control bus, and a status signal bus, etc. However, for the sake of clarity, all kinds of buses are labeled as bus 840 in the figure.

[0117] The processor 810 may be composed of at least one general-purpose processor, such as a CPU, or a combination of a CPU and a hardware chip. The above-mentioned hardware chip may be an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. The processor 810 executes various types of digital storage instructions, such as digital storage instructions in software or firmware programs stored in the memory 830, and it enables the electronic device 800 to provide various services.

[0118] The memory 830 is used to store program codes, and is controlled by the processor 810 to execute the processing steps of the data reconciliation method in the above embodiments. The program codes may include one or more software modules, and these one or more software modules may be Figure 7 the software modules provided in the embodiments, such as a receiving unit, a determining unit, a sending unit, and a generating unit. The receiving unit is used to receive the metadata update information of the first service system in multiple service systems in the cloud platform. Among them, multiple service systems all include a target metadata database, and the metadata update information indicates that the target metadata database of the first service system has updated the first metadata. The determining unit is used to reconcile the metadata in the target metadata databases of multiple service systems, and determine the second service system in which the first metadata in the target metadata database has not been updated. The sending unit is used to send a notification message for updating the first metadata to the second service system. The generating unit is used to generate a first structured query statement, and the first structured query statement is used to indicate that the reconciliation range is the first range.

[0119] The memory 830 may include volatile memory, such as random access memory (RAM); the memory 830 may also include non-volatile memory (NVM), such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); the memory 830 may further include a combination of the above types. The memory 830 may store program code, specifically executing Figure 3 the steps S310 - S330 and their optional steps in the embodiments, which will not be elaborated here.

[0120] The communication interface 820 may be an internal interface (such as a high-speed serial computer expansion bus), a wired interface (such as an Ethernet interface), or a wireless interface (such as a cellular network interface or a wireless local area network interface) for communicating with other devices or modules.

[0121] It should be noted that Figure 8 This is merely a possible implementation manner of the embodiments of the present application. In practical applications, the electronic device 800 may further include more or fewer components, which are not limited here. Regarding the content not shown or described in the embodiments of the present application, reference may be made to the relevant elaborations in the foregoing Figure 5 embodiments, which will not be elaborated here.

[0122] It should be understood that this embodiment may be implemented by a general physical server, for example, an ARM server or an X86 server, or may also be implemented by a virtual machine based on a general physical server combined with NFV technology. A virtual machine refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment. The present application does not make specific limitations.

[0123] Figure 8 The illustrated electronic device 800 may also be a computer cluster composed of at least one server, which is not specifically limited in the present application.

[0124] The embodiments of the present application further provide a computer-readable storage medium, in which instructions are stored. When they run on a processor, Figure 3 the illustrated method flow is realized.

[0125] The embodiments of the present application further provide a computer program product. When the computer program product runs on a processor, Figure 3 the illustrated method flow is realized.

[0126] The above embodiments can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, the processes or functions described in the embodiments of the present invention are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, fiber optic, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that contains one or more collections of available media. The available media can be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as high-definition digital video discs (DVDs)), or semiconductor media. The semiconductor media can be SSDs.

[0127] As described above, the specific embodiments of the present invention are only described, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A data reconciliation method, characterized in that, the method includes: receiving metadata update information of a first business system among multiple business systems in a cloud platform, wherein the multiple business systems each include a target metadata database, and the metadata update information indicates that the target metadata database of the first business system has updated first metadata; reconciling the metadata in the target metadata databases of the multiple business systems to determine a second business system among the multiple business systems that has not updated the first metadata in the target metadata database; sending notification information for updating the first metadata to the second business system.

2. The method according to claim 1, characterized in that, the metadata change information includes a first range corresponding to the first metadata in the target metadata database; the reconciling the metadata in the target metadata databases of the multiple business systems includes: generating a first structured query statement for indicating that the reconciliation range is the first range; reconciling the metadata in the first range in the target metadata databases of the multiple business systems based on the first structured query statement.

3. The method according to claim 1 or 2, characterized in that, the metadata change information includes a metadata change event, and the metadata change event includes one or more of creating an instance, deleting an instance, changing an instance, deleting a backup, modifying a backup policy, and deleting a backup policy.

4. The method according to claim 2, characterized in that, the method further includes: sending the metadata in the first range in the target metadata databases of the multiple business systems to a data warehouse of a first type for reconciliation based on the first structured query statement, and the data warehouse of the first type includes an online analytical processing data warehouse.

5. The method according to claim 1, characterized in that, the multiple business systems include one or more of an instance management system, a backup management system, a resource management system, and a metering management system.

6. A data reconciliation method, characterized in that, applied to a cloud platform, the cloud platform includes multiple business systems and a reconciliation platform, wherein the multiple business systems each include a target metadata database, the method includes: a first business system among the multiple business systems sending metadata update information to the reconciliation platform, and the metadata update information indicates that the target metadata database of the first business system has updated first metadata; the reconciliation platform reconciling the metadata in the target metadata databases of the multiple business systems to determine a second business system among the multiple business systems that has not updated the first metadata; the reconciliation platform sending notification information for updating the first metadata to the second business system.

7. The method according to claim 6, characterized in that, the cloud platform further includes a data processing platform, and a first business system among the multiple business systems sending metadata update information to the reconciliation platform includes: a first business system among the multiple business systems sending metadata update information to the data processing platform; The data processing platform determines a first range corresponding to the first metadata in the target metadata database according to the metadata update information; The data processing platform sends the first range to the reconciliation platform; and The reconciliation platform reconciles the metadata in the target metadata databases of the multiple business systems, including: The reconciliation platform generates a first structured query statement, which is used to indicate that the reconciliation range is the first range; Based on the first structured query statement, the reconciliation platform reconciles the metadata within the first range in the target metadata databases of the multiple business systems.

8. The method according to claim 7, wherein, The data processing platform includes a data replication service, a streaming media platform, and a stream processing platform. The first business system among the multiple business systems sends metadata update information to the reconciliation platform, including: The first business system among the multiple business systems sends the metadata update information to the data replication service; The data replication service sends the metadata update information to the stream processing platform through the streaming media platform; The stream processing platform determines a first range corresponding to the first metadata in the target metadata database according to the metadata update information; The stream processing platform sends the first range to the reconciliation platform.

9. A cloud platform, wherein, The cloud platform includes multiple business systems and a reconciliation platform. Among them, each of the multiple business systems includes a target metadata database, The first business system among the multiple business systems is used to send metadata update information to the reconciliation platform, and the metadata update information indicates that the target metadata database of the first business system has updated the first metadata; The reconciliation platform is used to reconcile the metadata in the target metadata databases of the multiple business systems, and determine a second business system among the multiple business systems that has not updated the first metadata; The reconciliation platform is further used to send notification information for updating the first metadata to the second business system.

10. An electronic device, wherein, It includes a processor and a memory. The memory is used to store instructions, and the processor is used to execute the instructions. When the processor executes the instructions, it executes the method according to any one of claims 1 to 8.

11. A computer-readable storage medium, wherein, It includes instructions. When the instructions run on an electronic device, the electronic device is caused to execute the method according to any one of claims 1 to 8.

Images