If the 'things' in IoT are to operate / be manufactured universally, there should be a universal messaging scheme.Agreeing on new standards (or sticking to existing standards) of message structure, will go a long way in generalising the cloud based applications being developed for IoT.
The questions is "what is the structure of the messages being transmitted by the 'things'?"
Although micro services and allied messaging fabrics are being developed, it defines only a framework of communication between services and their independent interoperability.
It is to be remembered that each 'thing' is a chunk of electronic hardware that runs on a firmware/application coded into it. Hence it becomes imperative for all the 'things' to understand what other 'things' convey. Under the roof of a very small IoT deployment, like a production plant, it may be not challenging to confront the issue. But when it comes to global operation, the control over messaging formats is certainly necessary.
If the 'things' in IoT are to operate / be manufactured universally, there should be a universal messaging scheme.Agreeing on new standards (or sticking to existing standards) of message structure, will go a long way in generalising the cloud based applications being developed for IoT.
Say Mr.X's cloud services could seamlessly operate on Mr. Z's devices, via Mr.Y's micro services fabric middleware, while all three of them are unaware of each other's solutions.
Message standardisation has to be meticulously done and grouped/categorised, because key words and terminologies keep changing from one application to another. This is an intriguing challenge.