In some examples, a computing device may communicate with a plurality of network storage systems, such as a first network storage system provided by a first service provider employing a first storage protocol and a second network storage system provided by a second service provider employing a second storage protocol different from the first storage protocol. The computing device receives a first object, and determines, for the first object, a first remote bucket at the first network storage system and a second remote bucket at the second network storage system. The computing device may add a synchronization event to a queue for replicating the first object to the first remote bucket and the second remote bucket. Based on consuming the synchronization event from the queue, the computing device replicates data and metadata of the first object to the first remote bucket and the second remote bucket.

Data storage system conflict management techniques are described. In one example, data is sent by client devices to both a repository system and a search index system of a data storage system. Each of the client devices maintains, locally, records of changes to data of the repository system, e.g., through use of an invertible Bloom lookup table. The records are used as a basis by the client devices to send reports to an arbiter system and used to detect conflicts When detected, a conflict request is communicated to client devices involved in the conflict as well as to the repository system and responses used to generate a correction that is communicated to update the repository system and search index system.

Technology for interoperability is disclosed by enabling the sharing of application state data for an application experience across computing devices, operating systems, applications, or locations. In one aspect, a secondary application shares encrypted state data along with a non-encrypted hint that describes the application experience reflected in the state data with a primary application. The primary application is then able to use the hint to determine that a user is interested in returning to the experience in the secondary application. The primary application then transfers the encrypted state data to the secondary application, which uses the state data to return the application to the application experience. A platform and an application programming interface (API) are provided for computer applications and services to store and retrieve application state data associated with an event.

The subject matter described herein provides techniques to ensure that queries of a distributed database observe a consistent read of the database without locking or logging. In this regard, next-write timestamps uniquely identify a set of write transactions whose updates can be observed by reads. By publishing the next-write timestamps from within an extendable time lease and tracking a “safe timestamp,” the database queries can be executed without logging read operations or blocking future write transactions, and clients issuing the queries at the “safe timestamp” observe a consistent view of the database as it exists on or before that timestamp. Aspects of this disclosure also provide for extensions, done cheaply and without the need for logging, to the range of timestamps at which read transactions can be executed.

The invention includes a method for monitoring an automated plant having at least one field device, wherein a first cloud-capable database, having a first data configuration and containing field device related data including measured values, parameter values, identification data, and diagnostic status of the field device, wherein a second cloud-capable database having a second data configuration incompatible with the first data configuration, and wherein the first and the second data configurations define file formats of the data, the method comprises: retrieving at least a part of the data contained in the first database by means of a data conversion unit, especially an edge device or a gateway; converting the retrieved data into a format conforming to the second data configuration; and storing the converted data in the second database. The invention further includes a data conversion unit, which is embodied for executing the method of the invention.

Embodiments of the present disclosure provide a method, a computer program product and apparatus for processing transactions in a synchronized replication system, wherein the method comprises, at a source site in the synchronized replication system: serializing commits of transactions in the synchronized replication system so that only one of the transactions can be committed at the same time; in response to initiating the commit of the one transaction, generating a log for each of transactions that are ongoing in the synchronized replication system, so as to record impact of all operations of a respective transaction on the synchronized replication system; marking transactions for which the logs have been generated; and completing commits of the marked transactions.

An example of communicating transaction data between a first service and a second service includes receiving transactions of first service, and processing the received transactions and storing the results in a database of the first service. For at least some of the received transactions, corresponding transaction messages are produced for processing by the second service, and tracking that each of the transaction messages is provided to a message queue. The transaction messages are received from the message queue and are processed using the second service, and the results are stored in a database of the second service. When there are duplicate transaction messages received from the message queue, the database of the second service only stores the results of one of the duplicate transaction messages.

A distributed database compaction system can perform compaction for transactional queries in an asynchronous matter without affecting completion of the queries. The compaction system can implement asynchronous transformation of key pairs in the database, and older keys can be periodically purged using a scheduled compactor. Subsequent queries use the compacted stored keys to perform efficient queries with direct reads of committed transactions and more efficient access to key values stores of the distributed database.

Techniques and structures to synchronize hierarchical data, comprising. A conflict between data stored at a computing device and data stored at a service provider database is detected. A synchronization operation is performed to synchronize a plurality of objects within the hierarchical entity data stored at the computing device with hierarchical entity data stored at the service provider database.

A server may support an aggregation service for a multitenant system. The service may support a method for data processing that includes determining that a plurality of tenants of a multitenant database system correspond to a common entity, where each tenant is associated with a respective instance of a cloud platform that services data from a corresponding database instance. The method may further include provisioning a new database instance for the common entity, generating a connector that is configured to access data of the corresponding database instance, generating a schema for the new database instance that aggregates the data of each database instance accessed by the connector, and instantiating a new cloud platform instance that is configured to access the schema of the new database instance, where the new cloud platform instance is configured to serve data queried from the schema of the new database instance via a client application.