is there an api in that (iot)?
DESCRIPTION
An opinionated investigation into the impact of the Internet of Thing on APIs. What will remain and what will change? How will the future API design, protocols and developer experience be impacted by the promises and limitations of IoT. If you are wondering if IoT is hype or reality and how you will integrate it with it from an API perspective this talk is for you. This presentation will get you an (admittedly) opinionated overview over the current state of the art and possible future direction of APIs in IoT.TRANSCRIPT
Is there an API in that (IoT) @ APIcon SF 2014
Holger [email protected]@ca.com
Use with caution – opinions ahead!
How a talk about the Internet of Things usually starts ..
Billions of devicesTrillions of Dollar
in 2016, 2018, 2020, 2025, 2030 .. I call it the (x+1) syndrom
Usually followed by
Smart *
* = cities, grid, buildings, homes, trashcans, fridges, lights, toasters, toilets … scales (?)
Followed by
It will make you *
* = better, faster, more safe, more efficient, more happy, more beautiful, more successful …
Depressing
Did someone mention …
Most people worldwide live within a couple of miles of a rail road
(we will get back to that in a few minutes)
Designing an API is easy Effective API design is difficult
The API Value Chain
Effective API Design
The Internet of Things
Cloud
Sensors & Actuators
Mobile/App
Marketplace
ServerGateway
ServerGateway
Mobile/App
Server
Gatew
ay
ServerGateway
ServerGateway
Overlapping Domains of Interest (Clustered Graphs)
Mobile/App
Mobile/App
Mobile/App
Domain A
Domain B
Domain C = A ∩ B
Domain E = C ∩ …
tem
po
ral d
ime
nsio
n
spacial dimension
How we see the Internet of Things
Wouldn’t it be better to call it an Internet of Gateways?
How we see the Internet of Things
Courtesy of http://makerbot.com
How the rest sees the Internet of Things
+
Courtesy of http://goodnightlamp.com
How will the Internet of Things shape API design?
Low powerLimited bandwidth
Many messagesAsynchronousAutonomous
Many connected applications/systems
Internet of Things Characteristics
Lots of frameworks
Lots of protocols
Lots of SDKs
http://www.layer7tech.com/blogs/index.php/sdks-work-until-they-dont/
https://www.linkedin.com/groups/IBM-has-been-dominating-press-108418.S.239593910
Lots of passion
Low power?Limited bandwidth?
Many messages?AsynchronousAutonomous
Many connected applications/systems?
Internet of Things Characteristics
Where is your Thing going to be?
Home or Office or (Green)FieldMobile or StationaryWearable or Built-in
Autonomous or Always Connected
Does every Thing need a digital shadow in the cloud?
Is sending data cheaper than calculating locally?
Remembering Why This Whole API Thing Is Working
SimplicitySelf-Service
Low barrier to useAccess to valuable resources
http://apievangelist.com/2014/05/06/remembering-why-this-whole-api-thing-is-working--apidays-berlin/
Does IoT make API design
an afterthought?
Effective API Design