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.
11. • Informaton
• Product
• Service
Business
Asset
• API
• SLA
• EULA
API Provider
• Building
App
Developer
• Using API
Application
• Using App
End-User
The API Value Chain
12. • Informaton
• Product
• Service
Business
Asset
• API
• SLA
• EULA
API Provider
• Building
App
Developer
• Using API
Application
• Using App
End-User
Effective API Design
27. Remembering Why This Whole API Thing Is Working
Simplicity
Self-Service
Lowbarrier to use
Access to valuable resources
http://apievangelist.com/2014/05/06/remembering-why-this-whole-api-thing-is-working--apidays-berlin/
29. • Informaton
• Product
• Service
Business
Asset
• API
• SLA
• EULA
API Provider
• Building
Thing
Maker
• Using API
Thing
• Using
Thing
End-User
Effective API Design
Notas do Editor
When API strategies fail, it is often because one or more of the links in this value chain are too weak to support the creation of a healthy API economy.
If there is nothing of value in the business assets, the API won’t succeed.
Woods, Dan; Jacobson, Daniel; Brail, Greg (2011-12-19). APIs: A Strategy Guide (p. 23). OReilly Media - A. Kindle Edition.
When API strategies fail, it is often because one or more of the links in this value chain are too weak to support the creation of a healthy API economy.
If there is nothing of value in the business assets, the API won’t succeed.
Woods, Dan; Jacobson, Daniel; Brail, Greg (2011-12-19). APIs: A Strategy Guide (p. 23). OReilly Media - A. Kindle Edition.
ASP.NET SignalR is a library for ASP.NET using Websockets to add real-time web functionality to your applications.
Socket.IO is a JavaScript library for realtime web applications. It has two parts: a client-side library that runs in the browser, and a server-side library for node.js.
https://www.meteor.com/blog/2012/03/21/introducing-ddp
Pub Sub: MQTT, XMPP, CoAP, REST, STOMP
http://mholdmann.wordpress.com/2013/05/17/the-choice-of-protocol-for-iot-and-m2m-will-dictate-the-emergence-and-success-of-the-market/
CoAP:
The CoRE group has proposed the following features for CoAP:RESTful protocol design minimizing the complexity of mapping with HTTP.Low header overhead and parsing complexity.URI and content-type support.Support for the discovery of resources provided by known CoAP services.Simple subscription for a resource, and resulting push notifications.Simple caching based on max-age.The mapping of CoAP with HTPP is also defined
MQTT:
It offers three qualities of service: 1) fire-and-forget / unreliable,2) “at least once” to ensure it is sent a minimum of one time (but might be sent more than one time), and 3) “exactly once”.MQTT’s strengths are simplicity (just five API methods), a compact binary packet payload (no message properties, compressed headers, much less verbose than something text-based like HTTP), and it makes a good fit for simple push messaging scenarios such as temperature updates, stock price tickers, oil pressure feeds or mobile notifications.
STOMP:
A STOMP client is a user-agent which can act in two (possibly simultaneous) modes:as a producer, sending messages to a destination on the server via a SEND frameas a consumer, sending a SUBSCRIBE frame for a given destination and receiving messages from the server as MESSAGE frames.
When API strategies fail, it is often because one or more of the links in this value chain are too weak to support the creation of a healthy API economy.
If there is nothing of value in the business assets, the API won’t succeed.
Woods, Dan; Jacobson, Daniel; Brail, Greg (2011-12-19). APIs: A Strategy Guide (p. 23). OReilly Media - A. Kindle Edition.
Faye: Bayeux is a protocol for transporting asynchronous messages (primarily over HTTP), with low latency between a web server and web clients.
http://svn.cometd.org/trunk/bayeux/bayeux.html#toc_0