Abstract: A workflow service is provided on a cloud-based platform, such as a cloud foundry platform. An exemplary method comprises: providing a workflow service in a cloud-based platform, wherein the workflow service comprises a workflow executor service; obtaining, by the workflow service, a workflow configuration file specifying a sequence of tasks for execution by the workflow service; processing the workflow configuration file using the workflow executor service to create a workflow instance; initiating a given task from the workflow instance for execution by a task executor that publishes a status and/or any outputs of the given task as an event to an event source; monitoring the event source, using an event listener, to obtain the status and/or the outputs of the given task; and identifying a next task in the sequence based on the status of the given task.

Abstract: An Internet of Things (IoT) gateway service is provided on a cloud-based platform, such as a cloud foundry platform. An exemplary method comprises: providing an IoT gateway service in a cloud-based platform, wherein the IoT gateway service comprises a message broker; obtaining, by the IoT gateway service, a wireless communication from one or more sensor devices; converting the wireless communication to a message in a machine-to-machine IoT connectivity protocol; and providing the message to the message broker that determines a topic of the message and publishes the message to one or more client devices that have subscribed to the topic. A service broker may be created that wraps the IoT gateway service as a tile in the cloud-based platform. A configurable and vendor neutral open source implementation of the IoT gateway service is also provided.

Abstract: A method in one embodiment comprises: obtaining, by a first cloud-based IoT gateway service, a radio signal from a first mobile sensor device; converting the radio signal to a message in a machine-to-machine IoT connectivity protocol; and providing the message to a message broker that determines a topic of the message and publishes the message using the topic. The message is distributed to one or more additional mobile sensor devices using a content delivery network. The first mobile sensor device optionally obtains the radio signal from one or more additional mobile sensor devices by means of vehicle-to-vehicle communications. The radio signal comprises, for example, a distress signal of a given mobile sensor device and a K-Nearest Neighbor process is optionally used to identify other mobile devices in proximity to the given mobile sensor device.

Abstract: A method for processing queries includes a master device receiving a query from a client device, and interpreting the query to identify a data record identifier matching the query. The method further includes obtaining, using a metadata table on the master device, a segment device identifier storing a data record identified by the data record identifier for the query, sending the query to a segment device, the segment device being identified by the segment device identifier, and receiving a result of the query from the segment device. The method further includes transmitting the result to the client device.

Abstract: A method in one embodiment comprises: obtaining, by a first cloud-based IoT gateway service, a radio signal from a first mobile sensor device; converting the radio signal to a message in a machine-to-machine IoT connectivity protocol; and providing the message to a message broker that determines a topic of the message and publishes the message using the topic. The message is distributed to one or more additional mobile sensor devices using a content delivery network. The first mobile sensor device optionally obtains the radio signal from one or more additional mobile sensor devices by means of vehicle-to-vehicle communications. The radio signal comprises, for example, a distress signal of a given mobile sensor device and a K-Nearest Neighbor process is optionally used to identify other mobile devices in proximity to the given mobile sensor device.

Abstract: A workflow service is provided on a cloud-based platform, such as a cloud foundry platform. An exemplary method comprises: providing a workflow service in a cloud-based platform, wherein the workflow service comprises a workflow executor service; obtaining, by the workflow service, a workflow configuration file specifying a sequence of tasks for execution by the workflow service; processing the workflow configuration file using the workflow executor service to create a workflow instance; initiating a given task from the workflow instance for execution by a task executor that publishes a status and/or any outputs of the given task as an event to an event source; monitoring the event source, using an event listener, to obtain the status and/or the outputs of the given task; and identifying a next task in the sequence based on the status of the given task. A configurable and vendor neutral open source implementation of the workflow service is also provided.

Abstract: An IoT gateway service is provided on a cloud-based platform, such as a cloud foundry platform. An exemplary method comprises: providing an IoT gateway service in a cloud-based platform, wherein the IoT gateway service comprises a message broker; obtaining, by the IoT gateway service, a wireless communication from one or more sensor devices; converting the wireless communication to a message in a machine-to-machine IoT connectivity protocol; and providing the message to the message broker that determines a topic of the message and publishes the message to one or more client devices that have subscribed to the topic. In one or more embodiments, a service broker is created that wraps the IoT gateway service as a tile in the cloud-based platform. A configurable and vendor neutral open source implementation of the IoT gateway service is also provided.

Abstract: An integration engine is provided for communications between source and target applications. A message is sent from a source application to a target application, by processing a header element to route the message to the target application; transforming a message format of the message to a different message format; storing the message payload using a Claim-Check Enterprise Application Integration (EAI) pattern; and providing the transformed message to the target application. Transport adapters optionally transform a message format of the message to a different message format, such as a message format of the source application being transformed to a message format of the target application. The header element is optionally updated using a channel interceptor to update a next endpoint in a flow based on one or more business rules applied to the message payload. The header element can be processed by a header-based router that routes the message to a next endpoint in a flow.