Abstract: In various implementations, an asset gateway service receives log messages comprising asset data captured by a gateway device associated with an asset. The log messages each include a first identifier corresponding to a first representation of the gateway device, which itself is associated with a first organization. The service persists data from the log to a first datastore accessible by the first organization. The service also determines whether a second representation of the gateway device (i.e., a clone) exists. If so, the service persists at least some of the data from the log message to a second datastore, which itself may be associated with a second organization, thereby allowing both organizations to access the data in a secure yet convenient manner.

Abstract: A method comprising receiving first data from a first gateway device, determining that the first data includes an identifier of a first vehicle, and responsive to determining that the first data includes the identifier of the first vehicle, determining, based on the identifier of the first vehicle, that the first vehicle is a known vehicle in a fleet management system and responsive to determining, based on the identifier of the first vehicle, that the first vehicle is a known vehicle in the fleet management system, coupling the first gateway device with the first vehicle in the fleet management system, wherein the coupling causes data received from the first gateway device to be identified as data of the first vehicle.

Abstract: A computer system issues a batch read operation to a tablet in a first replication group in a distributed database and obtains a most recent version of data items in the tablet that have a timestamp no great than a snapshot timestamp T. For each data item in the one tablet, the computer system determines whether the data item has a move-in timestamp less than or equal to the snapshot timestamp T, which is less than a move-out timestamp, and whether the data item has a creation timestamp less than the snapshot timestamp T, which is less than or equal to a deletion timestamp.

Abstract: A system, computer-readable storage medium storing at least one program, and a computer-implemented method for performing operations on target servers is presented. A request including an operation is received. A set of target servers associated with the operation is identified. The following request processing operations are performed until a predetermined termination condition has been satisfied: a target server in the set of target servers to which the request has not been issued and whose health metrics satisfy health criteria is identified, the request to perform the operation is issued to the target server, and when the request to perform the operation fails at the target server, health metrics for the target server are updated to indicate that the request to perform the operation failed at the target server and health check operation is scheduled to be performed with respect to the target server.

Abstract: A computer system issues a batch read operation to a tablet in a first replication group in a distributed database and obtains a most recent version of data items in the tablet that have a timestamp no great than a snapshot timestamp T. For each data item in the one tablet, the computer system determines whether the data item has a move-in timestamp less than or equal to the snapshot timestamp T, which is less than a move-out timestamp, and whether the data item has a creation timestamp less than the snapshot timestamp T, which is less than or equal to a deletion timestamp.