Abstract: A gateway that may be implemented in a local network and that communicates with a cloud network to provide efficient services in a weakly connected setting is disclosed. The gateway may be configured to enable services that efficiently utilize resources in both of the gateway and the cloud network, and provide a desired quality of service while operating in a weakly connected setting. The gateway may provide data collection and processing, local network services, and enable cloud services that utilize data collected and processed by the gateway. The local network may include one or more sensors and/or video cameras that provide data to the gateway. In a further implementation, the gateway may determine an allocation of one or more tasks of a service between the gateway and a cloud network by determining the allocation of the one or more service tasks based on desired service latency.

Abstract: This document relates to data storage techniques. One example can buffer write commands and cause the write commands to be committed to storage in flush epoch order. Another example can maintain a persistent log of write commands that are arranged in the persistent log in flush epoch order. Both examples may provide a prefix consistent state in the event of a crash.

Abstract: A gateway that may be implemented in a local network and that communicates with a cloud network to provide efficient services in a weakly connected setting is disclosed. The gateway may be configured to enable services that efficiently utilize resources in both of the gateway and the cloud network, and provide a desired quality of service while operating in a weakly connected setting. The gateway may provide data collection and processing, local network services, and enable cloud services that utilize data collected and processed by the gateway. The local network may include one or more sensors and/or video cameras that provide data to the gateway. In a further implementation, the gateway may determine an allocation of one or more tasks of a service between the gateway and a cloud network by determining the allocation of the one or more service tasks based on desired service latency.

Abstract: Techniques and constructs to facilitate data management can provide improved response time and space efficiency for time-series data such as from connected devices. The constructs may enable receiving a stream of time-series data comprising a plurality of objects and a time identification associated with each of the objects. One or more tags are associated with the objects. The constructs may also chunk the stream into a plurality of contiguous chunks, each including a plurality of objects, create an index associating the time identification and the one or more tags, transmit the chunks to a first, remote storage, and then store the index.

Abstract: A gateway that may be implemented in a local network and that communicates with a cloud network to provide efficient services in a weakly connected setting is disclosed. The gateway may be configured to enable services that efficiently utilize resources in both of the gateway and the cloud network, and provide a desired quality of service while operating in a weakly connected setting. The gateway may provide data collection and processing, local network services, and enable cloud services that utilize data collected and processed by the gateway. The local network may include one or more sensors and/or video cameras that provide data to the gateway. In a further implementation, the gateway may determine an allocation of one or more tasks of a service between the gateway and a cloud network by determining the allocation of the one or more service tasks based on desired service latency.

Abstract: This document relates to data storage techniques. One example can buffer write commands and cause the write commands to be committed to storage in flush epoch order. Another example can maintain a persistent log of write commands that are arranged in the persistent log in flush epoch order. Both examples may provide a prefix consistent state in the event of a crash.

Abstract: Techniques and architectures may be used to generate data center network topologies that use less reliable and less expensive links mixed with links of higher reliability. Such topologies may be categorized into reliability classes, where each class corresponds to a bound(s) on reliability of paths that include the links. A topology class may be selected for use by an application based, at least in part, on the degree of reliability demanded by the application.

Abstract: This document relates to data storage techniques. One example can buffer write commands and cause the write commands to be committed to storage in flush epoch order. Another example can maintain a persistent log of write commands that are arranged in the persistent log in flush epoch order. Both examples may provide a prefix consistent state in the event of a crash.

Abstract: Maintaining high availability of objects for both read and write transactions. Secondary copies of cached objects are created and maintained on disks of a secondary caching node and in remote data storage. In response to an update request, the secondary copies of cached objects are updated. Secondary cached objects are synchronously invalidated in response to the update request, and the update is asynchronously propagated to a secondary caching node.

Abstract: Migration functionality is described herein for efficiently migrating application state information among user devices. The migration functionality operates by receiving factor information that describes a context in which a user is using an application on a first user device. For instance, the factor information may describe the manner in which the user has used the application on various user devices on prior occasions, together with characteristics of the user's current environment. The migration functionality then determines, based on the factor information, whether to transfer application state information from the first user device to at least a second user device. The application state information captures at least a dynamic runtime state of the application on the first user device.

Abstract: This document relates to data storage techniques. One example can buffer write commands and cause the write commands to be committed to storage in flush epoch order. Another example can maintain a persistent log of write commands that are arranged in the persistent log in flush epoch order. Both examples may provide a prefix consistent state in the event of a crash.

Abstract: Techniques and constructs to facilitate data management can provide improved response time and space efficiency for time-series data such as from connected devices. The constructs may enable receiving a stream of time-series data comprising a plurality of objects and a time identification associated with each of the objects. One or more tags are associated with the objects. The constructs may also chunk the stream into a plurality of contiguous chunks, each including a plurality of objects, create an index associating the time identification and the one or more tags, transmit the chunks to a first, remote storage, and then store the index.

Abstract: Maintaining high availability of objects for both read and write transactions. Secondary copies of cached objects are created and maintained on disks of a secondary caching node and in remote data storage. In response to an update request, the secondary copies of cached objects are updated. Secondary cached objects are synchronously invalidated in response to the update request, and the update is asynchronously propagated to a secondary caching node.