The present disclosure provides a generic multi-source heterogeneous large-scale data system, including a sync node config unit, an install & deployment unit, a block & pipelining unit, a unilateral sync unit, a bilateral sync unit and a correctness guarantee unit. The system operates on a middle layer which is above a node database layer and beneath an application logic layer. In a data synchronization process, a client end transmits captured local change information to a server end in accordance with a synchronization task plan; the server end receives and transfers the change information to an asynchronous parallel message processing mechanism to be stored in a corresponding message queue; the server end polls a local message queue for reading to-be-processed change information, and then performs subsequent data change in accordance with rules for heterogeneous data mapping, so as to maintain consistence of synchronized data objects between a source end and a target end. The system of the present disclosure operates independently in a manner parallel to local applications of a synchronous node, and provides a guarantee mechanism of relaxed transaction for Internet distributed multi-source heterogeneous data synchronization through collaboration of loose coupling.

Systems and methods are provided for synchronizing messages. The systems and methods include operations for: identifying a difference between a current state of a messaging application and a shared synchronization database, wherein the shared synchronization database is updated via a third-party application in response to the third-party application receiving, from a server, a notification related to the messaging application, the messaging application and the third-party application being implemented on a client device; retrieving information from the shared synchronization database to update the current state of the messaging application based on the identified difference; and transmitting, to the server by the messaging application, a request for content based on the update to the current state of the messaging application.

A computer system synchronizes data in an edge computing network. A leader node is elected from a plurality of nodes, wherein the plurality of nodes includes a plurality of follower nodes that each cast a single vote for a candidate node, and wherein the candidate node is elected as the leader node in response to the candidate node receiving votes from a majority of the nodes. The leader node receives a request from a follower node comprising data to be replicated across the nodes, and transmits the data to the other nodes. When a majority of nodes receive the data, the leader node transmits instructions to the nodes to cause each node to commit the data to a data log maintained by each node. Embodiments of the present invention further include a method and program product for synchronizing data in substantially the same manner described above.

Initiating recovery actions when a dataset ceases to be synchronously replicated across a set of storage systems, including: receiving, by at least one storage system among a plurality of storage systems implementing a symmetric input/output model for a synchronously replicated dataset, a request to modify the dataset; identifying one or more operations associated with the request to modify the dataset that have not been applied to at least one storage system of the plurality of storage systems; and responsive to a system fault among the plurality of storage systems synchronously replicating the dataset, applying a recovery action based on recovery information that identifies one or more operations that have not been applied to the plurality of storage systems.

In various embodiments, a computer-implemented method for supporting consistent secondary indexes, comprises receiving, at a first node, a write request comprising a data entry, storing the data entry in an in-memory structure separate from a primary structure for storing the data entry, generating, based on the data entry, a secondary index data entry for a secondary index, and transmitting the secondary index data entry to a second node for inclusion in the secondary index.

A system is provided for resolving data errors. The system is configured to obtain an erroneous data element received from a source system and generate a plurality of probable data values for the data element. For each probable data value of the plurality of probable data values, the system verifies whether the probable data value can be processed successfully by an Extract, Transform and Load (ETL) logic and by one or more target applications configured to process the data element. The system determines one of the probable data values as a suggested data value of the data element, based on the verification of the probable data values. The system outputs the suggested data value for processing by the ETL logic.

A tool for inter-process communication in a multi-tenant environment. The tool creates an advertisement file for each tenant of a plurality of tenants. The tool locks a plurality of synchronization files prior to incrementing a semaphore, wherein the plurality of synchronization files correspond to the plurality of tenants, and wherein locking the plurality of synchronization files ensure that the semaphore is only decremented once per tenant. The tool searches for a response file corresponding to a specific tenant, wherein the response file includes metadata related to an information channel for communication with the specific tenant and information depicting a communication protocol used corresponding to the specific tenant. The tool unlocks the plurality of synchronization files. The tool establishes a connection, wherein the connection comprises an encrypted communication channel between the specific tenant and the attachment process mediated by a daemon.

In some embodiments, a system for synchronizing content with client devices receives a request from a client device to synchronize operations pertaining to content items associated with a user account registered at the system. The request can include the operations and a cursor identifying a current position of the client in a journal of revisions on the system. Based on the operations, the system generates linearized operations associated with the content items. The linearized operations can include a respective operation derived for each of the content items from one or more of the operations. The system converts each respective operation in the linearized operations to a respective revision for the journal of revisions and, based on the cursor, determines whether the respective revision conflicts with revisions in the journal. When the respective revision does not conflict with revisions in the journal, the system adds the respective revision to the journal.

A data synchronization method includes: receiving a data synchronization request from a light node; the request including a block identifier; obtaining synchronization transaction data in the synchronization block according to the block identifier; the synchronization transaction data including transaction detail data and contract information; obtaining, from a database, a target data set corresponding to the synchronization transaction data; the target data set including read data or result data. The result data is obtained by processing the transaction detail data based on the contract information; and obtaining verification data corresponding to the synchronization transaction data, and transmitting the synchronization transaction data, the verification data, and the target data set to the light node; verifying by the light node, a validity of the synchronization transaction data and to-be-verified result data corresponding to the transaction detail data, based on the verification data and the target data set.

Replication of data from a primary computing system to a secondary computing system. The replication is single-threaded or multi-threaded depending on one or more characteristics of the data to be replicated. As an example, the characteristics could include the type of data being replicated and/or the variability on that data. Also, the multi-threading capabilities of the primary and secondary computing systems are determined. Then, based on the identified one or more characteristics of the data, the primary computing system decides whether to perform multi-threaded replication and the multi-threading parameters of the replication based on the one or more characteristics of that data, as well as on the multi-threading capabilities of the primary and secondary computing system.