Change management using a thing-model on an internet-of-things platform

1. A computer-implemented method, comprising:

receiving, from an Internet of Things (IoT) device over a distributed system, an IoT data packet of IoT data in a first data format;

determining, using an IoT data model of an IoT persistency service storing the IoT data in different data formats supporting different applications, that a second different data format of at least some of the IoT data is being used by at least one application;

transforming, using a transformation rule in the IoT data model, the IoT data packet in the first data format to the second different data format, wherein the transformation rule defines a transformation between different versions of IoT data, and wherein the transformation rule identifies whether one or both of local and non-local data are used in the transformation; and

storing, in the IoT persistency service, the IoT data packet in the second different data format.

2. The computer-implemented method of claim 1 , further comprising storing, in the IoT persistency service, the IoT data packet in the first data format.

3. The computer-implemented method of claim 1 , wherein transforming the IoT data packet in the first data format to the second different data format comprises:

determining, from the transformation rule, that the transformation is based entirely on locally-stored data; and

executing a data transformation module and using the locally-stored data to convert the IoT data packet from the first data format to the second different data format.

4. The computer-implemented method of claim 1 , wherein transforming the IoT data packet in the first data format to the second different data format comprises:

determining, from the transformation rule, that the transformation is based at least in part on non-locally-stored data; and

executing a data acquisition module operable to:

create, using the transformation rule and information in the IoT data packet, a third-party data request;

send, over the distributed system, the third-party data request to a third-party service;

receive, from the third-party service, third-party data; and

create, using at least the third-party data, the IoT data in the second different data format.

5. The computer-implemented method of claim 1 , further comprising:

receiving, from an application, a request for IoT data in a third different format;

determining, using the IoT data model of the IoT persistency service, that the IoT data is not available in the third different format;

transforming, using the transformation rule, the IoT data into the third different format;

optionally storing the IoT data in the third different format in the IoT persistency service; and

providing, to the application in response to the request, the IoT data in the third different format.

6. The computer-implemented method of claim 5 , wherein transforming the IoT data into the third different format comprises:

determining, from the transformation rule, that the transformation is based entirely on locally-stored data; and

executing a data transformation module and using the locally-stored data to convert the IoT data packet from the first data format to the second different data format.

7. The computer-implemented method of claim 5 , wherein transforming the IoT data into the third different format comprises:

determining, from the transformation rule, that the transformation is based at least in part on non-locally-stored data; and

executing a data acquisition module operable to:

create, using the transformation rule and information in the IoT data packet, a third-party data request;

send, over the distributed system, the third-party data request to a third-party service;

receive, from the third-party service, third-party data; and

create, using at least the third-party data, the IoT data in the second different data format.

8. A computer-implemented system, comprising:

memory storing:

persistency services storing different versions of IoT data; and

a model defining transformations of data between versions; and

a server interoperably coupled to the memory and performing operations comprising:

receiving, from an Internet of Things (IoT) device over a distributed system, an IoT data packet of IoT data in a first data format;

determining, using an IoT data model of an IoT persistency service storing the IoT data in different data formats supporting different applications, that a second different data format of at least some of the IoT data is being used by at least one application;

transforming, using a transformation rule in the IoT data model, the IoT data packet in the first data format to the second different data format, wherein the transformation rule defines a transformation between different versions of IoT data, and wherein the transformation rule identifies whether one or both of local and non-local data are used in the transformation; and

storing, in the IoT persistency service, the IoT data packet in the second different data format.

9. The computer-implemented system of claim 8 , the operations further comprising storing, in the IoT persistency service, the IoT data packet in the first data format.

10. The computer-implemented system of claim 8 , wherein transforming the IoT data packet in the first data format to the second different data format comprises:

determining, from the transformation rule, that the transformation is based entirely on locally-stored data; and

executing a data transformation module and using the locally-stored data to convert the IoT data packet from the first data format to the second different data format.

11. The computer-implemented system of claim 8 , wherein transforming the IoT data packet in the first data format to the second different data format comprises:

determining, from the transformation rule, that the transformation is based at least in part on non-locally-stored data; and

executing a data acquisition module operable to:

create, using the transformation rule and information in the IoT data packet, a third-party data request;

send, over the distributed system, the third-party data request to a third-party service;

receive, from the third-party service, third-party data; and

create, using at least the third-party data, the IoT data in the second different data format.

12. The computer-implemented system of claim 8 , the operations further comprising:

receiving, from an application, a request for IoT data in a third different format;

determining, using the IoT data model of the IoT persistency service, that the IoT data is not available in the third different format;

transforming, using the transformation rule, the IoT data into the third different format;

optionally storing the IoT data in the third different format in the IoT persistency service; and

providing, to the application in response to the request, the IoT data in the third different format.

13. The computer-implemented system of claim 12 , wherein transforming the IoT data into the third different format comprises:

determining, from the transformation rule, that the transformation is based entirely on locally-stored data; and

executing a data transformation module and using the locally-stored data to convert the IoT data packet from the first data format to the second different data format.

14. The computer-implemented system of claim 12 , wherein transforming the IoT data into the third different format comprises:

determining, from the transformation rule, that the transformation is based at least in part on non-locally-stored data; and

executing a data acquisition module operable to:

create, using the transformation rule and information in the IoT data packet, a third-party data request;

send, over the distributed system, the third-party data request to a third-party service;

receive, from the third-party service, third-party data; and

create, using at least the third-party data, the IoT data in the second different data format.

15. A non-transitory computer-readable medium storing one or more instructions executable by a computer system to perform operations, comprising:

receiving, from an Internet of Things (IoT) device over a distributed system, an IoT data packet of IoT data in a first data format;

determining, using an IoT data model of an IoT persistency service storing the IoT data in different data formats supporting different applications, that a second different data format of at least some of the IoT data is being used by at least one application;

transforming, using a transformation rule in the IoT data model, the IoT data packet in the first data format to the second different data format, wherein the transformation rule defines a transformation between different versions of IoT data, and wherein the transformation rule identifies whether one or both of local and non-local data are used in the transformation; and

storing, in the IoT persistency service, the IoT data packet in the second different data format.

16. The non-transitory computer-readable medium of claim 15 , the operations further comprising storing, in the IoT persistency service, the IoT data packet in the first data format.

17. The non-transitory computer-readable medium of claim 15 , wherein transforming the IoT data packet in the first data format to the second different data format comprises:

determining, from the transformation rule, that the transformation is based entirely on locally-stored data; and

executing a data transformation module and using the locally-stored data to convert the IoT data packet from the first data format to the second different data format.

18. The non-transitory computer-readable medium of claim 15 , wherein transforming the IoT data packet in the first data format to the second different data format comprises:

determining, from the transformation rule, that the transformation is based at least in part on non-locally-stored data; and

executing a data acquisition module operable to:

create, using the transformation rule and information in the IoT data packet, a third-party data request;

send, over the distributed system, the third-party data request to a third-party service;

receive, from the third-party service, third-party data; and

create, using at least the third-party data, the IoT data in the second different data format.

19. The non-transitory computer-readable medium of claim 15 , the operations further comprising:

receiving, from an application, a request for IoT data in a third different format;

determining, using the IoT data model of the IoT persistency service, that the IoT data is not available in the third different format;

transforming, using the transformation rule, the IoT data into the third different format;

optionally storing the IoT data in the third different format in the IoT persistency service; and

providing, to the application in response to the request, the IoT data in the third different format.

20. The non-transitory computer-readable medium of claim 19 , wherein transforming the IoT data into the third different format comprises:

determining, from the transformation rule, that the transformation is based entirely on locally-stored data; and

executing a data transformation module and using the locally-stored data to convert the IoT data packet from the first data format to the second different data format.