IoT Trends for 2018
IoT Trends for 2018
Expect more growth at the edge, an increase in digital twin adoption, and more open testbeds in the realm of IoT development in 2018.
Join the DZone community and get the full member experience.Join For Free
Last year I made the bold move to write-up the 2017 trends I thought would be important for the IoT industry and Eclipse IoT community. It seemed like a useful exercise so I thought a 2018 version is appropriate.
1. Edge/Fog/IoT Gateway Computing Will Continue to Gain Traction
It is not feasible that all IoT devices will be communicating directly with the cloud. The amount of data, network availability and latency, as well as security are some of the primary drivers for pushing IoT compute toward the edges of the network. For example, an IoT solution for an oil rig needs to work regardless of connectivity to the cloud.
Companies like Dell, who happen to see hardware for gateways, are announcing significant investments in edge computing. Silicon Valley VCs are now saying edge computing is the next big thing and potentially the end of cloud computing. FWIW, I don’t see cloud computing ending anytime soon.
I think we will continue to see Eclipse Kura and Eclipse ioFog being embraced for edge computing. In 2018, I hope we will see Eclipse Kura running Eclipse DeepLearning4J providing a great IoT machine learning platform at the edge.
2. Digital Twins Will Become a Thing
I expect to see the IoT industry talk more about the term digital twin. Most of the major IoT vendors claim support for digital twins: GE, IBM, Bosch, Amazon, and MS. It will be interesting to see if the IoT industry will agree to a common definition for digital twins and even some common standards. Some common standards would enable a more robust vendor ecosystem for digital twins.
For Eclipse IoT, the Eclipse Ditto project is a new project that provides a framework for managing and creating digital twins. The code based is from the Bosch implementation of their digital twin solution. You can check out their first milestone release.
3. Eclipse IoT Integration
The Eclipse IoT open source projects are maturing to the point where many are providing stable, production-ready functionality. We are seeing more and more interest in the community to focus on integration between the projects. I see this as a very positive sign and expect to see more cross-project collaborations in 2018. Is it possible the Eclipse IoT WG will organize the first Eclipse IoT release train in 2018? We'll see.
4. More Open IoT Testbeds
In 2017, the IoT WG launched two open IoT Testbeds: 1) Asset Tracking and 2) Industry 4 Production Performance Management. These testbeds have successfully demonstrated how open source and commercial solutions can be integrated to solve a real IoT problem. In 2018, I hope we see more end-user organizations proposing and leading testbeds that show how a community of vendors can solve their IoT requirements.
5. Technology to Watch in 2018
It is difficult to ignore the hype around blockchain. However, it has not been clear how blockchain technology scales up and down to meet the requirements of IoT. IOTA’s tangle technology seems to have an approach that may work for IoT. Robert Bosch Venture Capital announced that they have purchased IOTA tokens to invest in the future of IoT, which seems pretty significant.
Low-Power Wide-Area Network (LPWAN) technology also seems to be ready for wide adoption. There appears to be a lot of momentum around LoRaWAN. The Things Network community continues to drive forward an open source community for LoRaWAN. With more roots in the cellular industry, NB-IoT appears to be the alternative to LoRaWAN. Wide adoption of both technologies will be a positive influence on enabling more IoT use cases.
2018 will be another exciting year for IoT. My bold prediction is that 2018 is going to be the year that companies will start talking about their IoT success stories. Enjoy!
Published at DZone with permission of Ian Skerrett , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.