Site Tools


coapnativecloud

This is an old revision of the document!


OCF CoAP Native Cloud 2.0

Overview

What are the biggest problems in IoT? Where do current market IoT solutions fall short? How should IoT be considered? [2018]

Put another way, “What are the most common issues preventing companies from fully realizing the benefits of IoT?” This question was answered at DZone by 23 executives involved with the Internet of Things.

Most important observations:

  • Companies are not able, or do not have the talent, to complete the end-to-end solution.
  • The unrealized complexity of deployment and the lack of skills to do so.
  • Lack of seamless and secure data fabric platform.
  • Challenging to make something at scale while maintaining quality.
  • Creating scalable devices that connect to everything they need to.
  • Large amount of the data that will run the IoT will be stored in the cloud. cmswire.com

The IoT industry, across numerous market verticals, is at an impasse where customers are demanding increasing sophistication at lower prices. Given the complexity and importance of IoT, no single company can or should be dictating the path forward for the entire industry.

The only viable path forward is collaboration between companies and market verticals to collaborate on developing, testing and standardizing the non-differentiating functionality. The Open Connectivity Foundation is currently working to achieve that, however the device-cloud communication represents a unique challenge for the engineers involved because there has never been a historical need for engineers to become knowledgeable in both embedded systems and cloud native application development. The proposed solution to this problem is to emulate the container runtime interface (CRI) architecture and embody Conway’s law to establish a loose coupling between the “IoT code” (CoAP/iotivity cloud interface) and the portions of the system that are much more familiar to the cloud developers (ex: db/messaging/auth) which will also vary more depending on the use case.

<WRAP center round info 60%> “Throughout our history, it has always been standardization of components that has enabled creations of greater complexity” –Simon Wardley </WRAP>

Most important challenges

  • Embedded systems engineering and cloud native application development are likely orthogonal skill sets for the organizations whose products would benefit the most from internet connectivity
  • The immense complexity of managing your own deployment means the market requires managed services
  • There is no seamless portability for IoT devices between clouds
  • Extremely important if we want to decouple the networking costs from hardware costs for customers, like we do for cell phones
  • Lack of an industry standard IoT cloud increases the attack surface of the industry

Design goals

  • Address these challenges in a way that is easy for companies and public clouds to adopt and offer as a managed service
  • Ensure a loose coupling between the database / messaging / auth and the OCF Native Cloud reference implementation
  • Provide an “official” backend that demonstrates how to integrate the database / messaging / auth and serve as the default choice for companies with common OLTP use cases

Domain Overview

<WRAP center round info 60%> The Internet of Things (IoT) is the network of physical devices, which are embedded with electronics, software, sensors, actuators, and connectivity for the purpose of enabling these things to connect and exchange data. Thus creating opportunities for more direct integration of the physical world into computer-based systems, resulting in efficiency improvements, economic benefits and reduced human intervention. (Wikipedia, Internet of Things) </WRAP>

In other words, an IoT device is regularly subject to change, since it represents the world around itUnderlined Text. It's up to the developer, how the world is represented through the device and processed by the application for your specific domain. Technology should support the transfer of data in a standardized and secured way. The IoT platform can't limit you and can't set boundaries, which would limit evolution of your system.

Domain is a sphere of knowledge, influence or activity.

IoT itself is most likely not a domain of your business, it is a group of technology achievements from the last decades of the 20th century, which open the door to new possibilities for your business domain. Allowing for the modelling of the external world specific to your needs, in the form of resources and events, which will be transferred in a secure and traceable manner to your application, located off-premise or even on-premise. The goal is for developers to focus primarily on the domain of their business.

coapnativecloud.1533795455.txt.gz · Last modified: 2018/08/09 06:17 by ondrej.tomcik