Patent classifications
G06F16/2322
Methods, apparatuses and computer program products for synchronizing data objects between and among application service systems
Various embodiments herein described are directed to methods, apparatuses and computer program products configured for improving data synchronization in on-premises application service systems. In some embodiments, an on-premises application service system may transmit a synchronization check message to an in-cloud application service system and receive a synchronization request message in response. Based at least in part on the synchronization request message, the on-premises application service system transmits data objects to the in-cloud application service system for synchronization. Additional example embodiments provide various example methods of managing synchronizations between on-premises application service systems and in-cloud application service systems that improve data security and reduce network traffic.
METHOD OF VERIFYING THAT A WAGER WAS PLACED BEFORE MARKET CLOSE
The present disclosure provides a method to determine if a user had placed a wager and verify that the wager was placed before the wagering market closed in a play-by-play wagering network. This method provides the ability to receive a wager from a user and allows the wagering network to receive a timestamp from the user's device to determine if the wager was placed before the market closing. Also, this method provides the ability to verify that there is no fraud, malicious activity, or cheating from the user by verifying that through a 3rd party network, such as the user's network connecting the user to the internet, that the timestamps provided by the network are correct and allowing the user to confirm their wager if received a few moments after the market has closed.
Adaptively updating databases of publish and subscribe systems using optimistic updates
An example system includes a processor to receive updates for a database of a publish and subscribe system. The processor is to generate an optimistic update based on the received updates. The processor is also to adaptively update the database using the optimistic update. In some examples, the processor generates a bulk optimistic update based on the optimistic update and adaptively updates the database using the bulk optimistic update or a read-modify-write sequence.
Image-based productivity tracking system
A work machine including a sensing device, a user interface, and a control unit is disclosed. The control unit may be configured to generate a productivity layer based on productivity data, and generate an image layer based on image data. The image data may include information relating to an image corresponding to a state of an operation associated with a worksite and a geospatial reference associated with the image. The control unit may be configured to generate a composite image of the worksite based on a map layer, the image layer, and the productivity layer, and cause the composite image to be displayed via the user interface. The composite image may position the image layer relative to the map layer based on the geospatial reference and geographical coordinates corresponding to the geospatial reference, and position the productivity layer relative to the image layer.
Reconfiguring a vehicle for transfer from a first operator to a second operator
A method is provided for reconfiguring a vehicle for transfer from a first operator to a second operator. The method includes accessing first datasets that define an initial configuration of the vehicle, importing second datasets that describe maintenance, repair or service of the vehicle during in-service operation with the first operator, and generating a first composite dataset defining a current configuration of the vehicle. The method also includes accessing third datasets that define requirements of the vehicle for in-service operation with the second operator, and generating a second composite dataset that defines a target configuration of the vehicle from the first composite dataset and based on data of the third datasets. The method includes comparing the first and second composite datasets to identify modifications to reconfigure the vehicle from the current configuration to the target configuration, and generating a visual presentation of the modifications to facilitate reconfiguration of the vehicle.
Time-based data retrieval prediction
Techniques are disclosed relating to determining a predicted time interval for querying a database beginning at a starting point in time to retrieve a specified number of records. A computer system receives a request for records from a database that stores timestamped records, where the request is for a specified number of records beginning at a starting point in time. The computer system then determines a predicted time interval for querying the database beginning at the starting point in time to retrieve the specified number of records, where the predicted time interval may be determined by a machine learning module that is trained using historical database transaction data. Such techniques may advantageously improve the efficiency of individual queries in fetching a desired amount of data from a database for applications.
OPERATING A STORAGE SERVER WITH A STORAGE VOLUME
A method, computer system, and a computer program product for operating at least one storage server. The present invention may include receiving an access request for at least one storage volume of at least one storage server. The present invention may include collecting data for the at least one storage volume, wherein the at least one storage volume has a corresponding unique volume identifier. The present invention may include storing at least the data for the at least one storage volume and the unique volume identifier in a database, the data being comprised of metadata and subset data, wherein the metadata is comprised of configuration and status information for the at least one storage volume, and wherein the subset data is a set of predefined selection criteria based on a respective computer server.
Event context enrichment
A database structure and a system that uses the structure to facilitate efficient context enrichment of low-level events occurring in a distributed computing system. In one aspect, the database structure comprises a table accessible to a distributed storage system. The table comprises a plurality of rows. Each row represents a corresponding process creation event of a particular process at a particular host at a particular time and assigned a particular event identifier. Each row comprises a row key identifying the particular host, the particular process, the particular time, and the particular event identifier of the process creation event corresponding to the row. The particular time and the particular event identifier are stored as part of the row key in a bitwise one's complement format. The row key structure facilitates efficient identification of a process creation event where only hostname and the process identifier of the process creation event are known.
Time reservations for ensuring consistent reads in a distributed database without logging
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.
FAST RECOVERY AND REPLICATION OF KEY-VALUE STORES
A key-value engine of a storage system may perform a restart recovery after a system failure. The key-value engine may read a metadata log to locate a latest system checkpoint, and load a page mapping table from the latest system checkpoint. The key-value engine may replay to apply changes to the page mapping table from a system transaction log starting from a system transaction replay starting point. The key-value engine may further form one or more read-only replicas using an underlying file stream opened in a read-only mode during the recovery after the system failure to further facilitate fast recovery and provide fast response to user transactions that conduct read only transactions after the system failure.