Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

IoT Is an Opportunity for API Deployment as Well as Consumption

DZone's Guide to

IoT Is an Opportunity for API Deployment as Well as Consumption

The Internet of Things is in a unique position to capitalize on APIs. As both a provider and consumer, see how the latest wave of connected devices could be a boon to API enthusiasts.

· IoT Zone
Free Resource

Learn how Bluetooth mesh helps you create industrial-grade networks. Download the mesh overview.

Overall, I am pretty underwhelmed by the Internet of Things. Most of the ways in which devices are being connected to the Internet are not very interesting, if not just a bad idea. Even with the overwhelming ways in which I am being underwhelmed by IoT, there are a handful of areas that I do find interesting, like industrial implementations, drones, and the general potential of the concept when you do it thoughtfully and securely.

One of the differences between IoT and the other areas that are fueling APIs in 2016 is that they can be both an API provider as well as an API consumer. While mobile applications have historically been the biggest driver of API development, they are just API consumers, as are most websites. There is a handful of API aggregation and integration as service providers who consumer APIs, then also provide APIs who pay this forward (sadly not all API service providers do this), but in the end, most endpoints are just consumers.

When it comes to IoT devices, this is where it gets interesting to me. These Internet-enabled devices can be both API consumers, and API providers — which I think everyone should be, but that is another dimension to this conversation. Deploying Linux, virtualized containers like Docker, and a web server on Raspberry Pi and other popular IoT devices is pretty trivial. This opens up the ability to not just send and receive data to the cloud via APIs, but also a number of possibilities for redefining the network — where APIs are not just about the current incarnation of cloud APIs.

I'm not saying that all implementations of IoT devices in this way will be interesting, but It does evolve the definition of what is possible when it comes APIs, especially when you couple this with the expanding definition of what is the network (ie. cellular, mesh, SDN, etc.). However, it does also continue expanding the attack surface area when it comes to IoT security, but I'm sure everyone is thinking deeply on this subject when it comes to evaluating whether or not a device should be connected to the network at all.

For a deeper look into Bluetooth mesh, check out this technical insight for developers.

Topics:
development ,provider ,api development ,service ,consumers

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}