Abstract: An example Internet of Things (IoT) sensor application hosted on a mobile device is configured to add the mobile device as a data sensor or source in the IT system. The IoT sensor application is configured to provide an interface between an input or output component of the mobile device and a data pipeline or application and/or to cloud data storage associated with an IoT system. The IoT sensor application is configured to connect to an edge device of the IoT system and search for a data source identifier associated with the type of data source component, and corresponding application(s) and/or data pipeline(s) to which the data source is connected. Once connected, the IoT sensor application provides captured data to or receives processed or playback data from the data source.

Abstract: An example Internet of Things (IoT) sensor application hosted on a mobile device is configured to add the mobile device as a data sensor or source in the IoT system. The IoT sensor application is configured to provide an interface between an input or output component of the mobile device and a data pipeline or application and/or to cloud data storage associated with an IoT system. The loT sensor application is configured to connect to an edge device of the IoT system and search for a data source identifier associated with the type of data source component, and corresponding application(s) and/or data pipeline(s) to which the data source is connected. Once connected, the IoT sensor application provides captured data to or receives processed or playback data from the data source.

Abstract: An example Internet of Things (IoT) sensor application hosted on a mobile device is configured to add the mobile device as a data sensor or source in the IoT system. The IoT sensor application is configured to provide an interface between an input or output component of the mobile device and a data pipeline or application and/or to cloud data storage associated with an IoT system. The IoT sensor application is configured to connect to an edge device of the IoT system and search for a data source identifier associated with the type of data source component, and corresponding application(s) and/or data pipeline(s) to which the data source is connected. Once connected, the IoT sensor application provides captured data to or receives processed or playback data from the data source.

Abstract: An example Internet of Things (IoT) sensor application hosted on a mobile device is configured to add the mobile device as a data sensor or source in the IoT system. The IoT sensor application is configured to provide an interface between an input or output component of the mobile device and a data pipeline or application and/or to cloud data storage associated with an IoT system. The IoT sensor application is configured to connect to an edge device of the IoT system and search for a data source identifier associated with the type of data source component, and corresponding application(s) and/or data pipeline(s) to which the data source is connected. Once connected, the IoT sensor application provides captured data to or receives processed or playback data from the data source.

Abstract: A resource manager directs cache operating states of virtual machines based on cache resource latency and by distinguishing between latencies in flash memory and latencies in network communications and by distinguishing between executing read commands and executing different types of write commands. As a result, the resource manager can downgrade the cache operating state of the virtual machines differently based on the type of latency being experienced and the type of command being performed. The resource manager can upgrade and/or reset the cache operating state of the virtual machines, when appropriate, and can give priority to some virtual machines over other virtual machines when operating in a downgraded cache operating state.

Abstract: When a virtual machine sends a write command to a host operating system, a cache system stores the record included in the write command and later sends the write command to a storage system. Systems and methods store an indication of when the write command was received along with the received records in the cache. The cache system determines an order of the records from the indication. In some instances, records received at the same time are serialized and/or assigned record numbers. The simultaneously received records can be assigned a batch number. According to the determined order, the records are retrieved from the cache memory and included in write commands sent to the storage system. In some instances, checkpoints can be stored to prevent records from being re-sent to the storage system following a failure.

Abstract: A resource manager directs cache operating states of virtual machines based on cache resource latency and by distinguishing between latencies in flash memory and latencies in network communications and by distinguishing between executing read commands and executing different types of write commands. As a result, the resource manager can downgrade the cache operating state of the virtual machines differently based on the type of latency being experienced and the type of command being performed. The resource manager can upgrade and/or reset the cache operating state of the virtual machines, when appropriate, and can give priority to some virtual machines over other virtual machines when operating in a downgraded cache operating state.

Abstract: When a virtual machine sends a write command to a host operating system, a cache system stores the record included in the write command and later sends the write command to a storage system. Systems and methods store an indication of when the write command was received along with the received records in the cache. The cache system determines an order of the records from the indication. In some instances, records received at the same time are serialized and/or assigned record numbers. The simultaneously received records can be assigned a batch number. According to the determined order, the records are retrieved from the cache memory and included in write commands sent to the storage system. In some instances, checkpoints can be stored to prevent records from being re-sent to the storage system following a failure.

Abstract: An apparatus and method for off-loading application components to edge servers are provided. An application is made edge-aware by defining which components of the application may be run from an edge server, and which components cannot be run from an edge server. When a request is received that is to be processed by an application on an origin server, a determination is made as to whether the application contains edgable components. If so, an edgified version of the application is created. When a request is received that is handled by a component that may be run on the edge server, the request is handled by that component on the edge server. When a request is received that is handled by a component that is not edgable, the request is passed to a proxy agent which then provides the request to a broker agent on the origin server.

Abstract: An apparatus and method for off-loading application components to edge servers are provided. An application is made edge-aware by defining which components of the application may be run from an edge server, and which components cannot be run from an edge server. When a request is received that is to be processed by an application on an origin server, a determination is made as to whether the application contains edgable components. If so, an edgified version of the application is created. When a request is received that is handled by a component that may be run on the edge server, the request is handled by that component on the edge server. When a request is received that is handled by a component that is not edgable, the request is passed to a proxy agent which then provides the request to a broker agent on the origin server.

Abstract: An apparatus and method for off-loading application components to edge servers are provided. An application is made edge-aware by defining which components of the application may be run from an edge server, and which components cannot be run from an edge server. When a request is received that is to be processed by an application on an origin server, a determination is made as to whether the application contains edgable components. If so, an edgified version of the application is created. When a request is received that is handled by a component that may be run on the edge server, the request is handled by that component on the edge server. When a request is received that is handled by a component that is not edgable, the request is passed to a proxy agent which then provides the request to a broker agent on the origin server.