Embed Size (px)
Citation preview
How will the Internet of Things shape API design?
Designing an API is easy Effec1ve API design is difficult
From xkcd.com
Effec1ve =
Mee;ng Our Business Objec;ves
• Informaton • Product • Service
Business Asset
• API • SLA • EULA
API Provider • Building
App
Developer
• Using API
Application • Using App
End-User
The API Value Chain
• Informaton • Product • Service
Business Asset
• API • SLA • EULA
API Provider • Building
App
Developer
• Using API
Application • Using App
End-User
Effec1ve API Design
Low power Limited bandwidth Many messages Asynchronous Autonomous
Many connected applica;ons/systems
Internet of Things Characteris1cs
Lots of frameworks
Lots of protocols
https://www.linkedin.com/groups/IBM-has-been-dominating-press-108418.S.239593910
Lots of passion
Low power? Limited bandwidth? Many messages?
Asynchronous Autonomous
Many connected applica1ons/systems?
Internet of Things Characteris1cs
Low power? Limited bandwidth? Many messages?
Real;me APIs Hypermedia APIs
Many connected applica1ons/systems?
Internet of Things Characteris1cs
Where is your Thing going to be?
Home or Office or Outside Mobile or Sta;onary Wearable or Built-‐in
Autonomous or Always Connected
Does every Thing need a digital shadow in the cloud?
Is sending data cheaper than calcula1ng locally?
Does IoT make API design
an aCerthought?
Remember why this whole API thing is working
Simplicity Self-‐Service
Low barrier to use Access to valuable resources
http://apievangelist.com/2014/05/06/remembering-why-this-whole-api-thing-is-working--apidays-berlin/
• Informaton • Product • Service
Business Asset
• API • SLA • EULA
API Provider • Building
Thing
Maker
• Using API
Thing • Using
Thing
End-User
Remember effec1ve API Design
People buy products and services to get a "job" done.
Embrace #jtbd perspec1ve
Pick your technology (or provider)
Based on that “job”
