The present disclosure relates to systems and methods for matching electronic activities with record objects based on entity relationships. The method can include accessing a plurality of electronic activities, identifying an electronic activity, identifying a first participant associated with a first entity and a second participant associated with a second entity, determining whether a record object identifier is included in the electronic activity, identifying a first record object of the system of record that includes an instance of the record object identifier, and storing an association between the electronic activity and the first record object. The method can include determining a second record object corresponding to the second entity, identifying, using a matching policy, a third record object linked to the second record object and identifying a third entity, and storing, by the one or more processors, an association between the electronic activity and the third record object.

A computerized data transfer system allows data transfers to be initiated over a network between senders and recipients. Individual senders initiate data transfers over the network by selecting a recipient from a list at a sender device. The system includes a data store of sender specific recipients, a data transfer history data store of past transfers; and a master participant data store storing profiles of recipients for which transfers can be initiated. The system includes a computing device that for selected senders, retrieves entries of the data store of sender specific recipients, master participant data store and data transfer history data store; generates a predicted transfer profile for each recipient for the sender, based on past data transfers and the master participant data store to identify deviations therefrom; and updates the data store of sender specific recipients for the selected sender to update entries for recipients associated with identified deviations.

An example operation includes one or more of encrypting, by a transport, received data based on a first biometric associated with an occupant, unencrypting, by the transport, the encrypted data, based on a verification of a second biometric, wherein the second biometric is a continuum of the first biometric, and providing, by the transport, the unencrypted data to the occupant.

A data movement system is provided for moving data using a data-to-file-to-data movement path. The data movement system includes a source database, a target database, a configuration database, and a data movement server. The data movement is in communication with the source database, the target database, and the configuration database. The processor is configured to receive a configuration record including source details and target details. The processor is also configured to define an extraction query based on the source details and to apply the extraction query to the source database to obtain an extraction load. The processor is further configured to generate a load file based on the extraction load, to define a load script based on the target details, and to apply the load script to the load file to obtain a load query. The processor is also configured to update the target database with the load query.

Embodiments of the invention are directed to database replication using heterogenous encoding. Aspects include obtaining a database and analyzing a data pattern of data in the database. Aspects also include identifying a plurality of candidate encoding formats and evaluating a computing cost for encoding the database for each of the plurality of candidate encoding formats. Aspects further include selecting an encoding format from the plurality of candidate encoding formats based at least in part on the computing cost and storing a backup copy of the database using the encoding format.

A method for facilitating data synchronization across a plurality of platforms is provided. The method includes retrieving a change event, the change event corresponding to an event stream from a first platform; parsing the change event to identify a record and a data operation; examining a synchronization database to determine whether a corresponding record is persisted in a database of a second platform; inserting the record into the synchronization database when the corresponding record is not persisted in the platform, the inserted record including a change indicator; and updating, by using the synchronization database, the database of the second platform to include the record.

A first stack running on a processor receives the transaction data, reference data, and context data. The reference data is independent of the transaction and of a user. The context data is associated with the user but is independent of the transaction. The first stack strips the transaction of derivable data to obtain stripped data. The derivable data includes data that can be derived from the stripped data, the context data, and the reference data. The derivable data can stream the stripped data to a global database available and redundant across multiple geographical regions. After the first stack fails, a second stack can resume the transaction by retrieving the stripped data from the global database, and retrieving the context data, and the reference data. The second stack can recreate the transaction data based on the stripped data, the context data, and the reference data, and can resume the transaction.

Techniques for request throttling in a provider network environment are described. A throttle handler controls whether requests will be processed through maintaining a token-based record, per type of request, having a token value indicative of a number of requests that can be processed over a time period. For a request, the token value of the token-based record corresponding to the request type is updated based on calculating an elapsed time between a last update time of the token-based record and the current time, calculating an intermediate token value as the existing token value plus a value of the elapsed time multiplied by a rate, and updating the token value to be the minimum between the intermediate token value and a burst value. The request is serviced when the updated token value is determined to be greater than or equal to a number of tokens needed to perform the request.

Source database precommitted transactions are resolved in a target database of a database replication system when selected source database precommitted transactions are subsequently aborted in the source database.

In some embodiments, a method includes generating, based on distributed ledger data associated with a first distributed ledger-based network (DLN), distributed ledger data associated with a second DLN. The first DLN and the second DLN each is a fork and the distributed ledger data associated with the first DLN include account data associated with a set of accounts. The method includes generating a request to initiate a transaction between a first account and a second account. The method includes authenticating the transaction based on a protocol associated with the second DLN and without using a private cryptographic key of the first account. The method includes sending a signal indicating the transaction was authenticated and storing information associated with the transaction in the distributed ledger data associated with the second DLN.