Is there an API in that (IoT)?
•Download as PPTX, PDF•
8 likes•2,797 views
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.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Is there an API in that (IoT)?
Similar to Is there an API in that (IoT)? (20)
More from CA API Management
More from CA API Management (20)
Recently uploaded
Recently uploaded (20)
Is there an API in that (IoT)?
- 1. Is there an API in that (IoT) @ APIcon SF 2014 Holger Reinhardt @hlgr360 holger.reinhardt@ca.com
- 2. Use with caution – opinions ahead!
- 3. How a talk about the Internet of Things usually starts ..
- 4. Billions of devices Trillions of Dollar in 2016, 2018, 2020, 2025, 2030 .. I call it the (x+1) syndrom
- 5. Usually followed by Smart * * = cities, grid, buildings, homes, trashcans, fridges, lights, toasters, toilets … scales (?)
- 6. Followed by It will make you * * = better, faster, more safe, more efficient, more happy, more beautiful, more successful …
- 7. Depressing
- 8. Did someone mention …
- 9. Most people worldwide live within a couple of miles of a rail road (we will get back to that in a few minutes)
- 10. Designing an API is easy Effective API design is difficult
- 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
- 13. The Internet of Things
- 14. Cloud Sensors & Actuators Mobile/App Marketplace Mobile/App Server Gateway Server Gateway Overlapping Domains of Interest (Clustered Graphs) Mobile/App Mobile/App Mobile/App Domain A Domain B Domain C = A ∩ B Domain E = C ∩ … temporaldimension spacial dimension How we see the Internet of Things Wouldn’t it be better to call it an Internet of Gateways?
- 15. How we see the Internet of Things Courtesy of http://makerbot.com
- 16. How the rest sees the Internet of Things + Courtesy of http://goodnightlamp.com
- 17. How will the Internet of Things shape API design?
- 18. Low power Limited bandwidth Many messages Asynchronous Autonomous Many connected applications/systems Internet of Things Characteristics
- 22. https://www.linkedin.com/groups/IBM-has-been-dominating-press-108418.S.239593910 Lots of passion
- 23. Low power? Limited bandwidth? Many messages? Asynchronous Autonomous Many connected applications/systems? Internet of Things Characteristics
- 24. Where is your Thing going to be? Home or Office or (Green)Field Mobile or Stationary Wearable or Built-in Autonomous or Always Connected
- 25. Does every Thing need a digital shadow in the cloud?
- 26. Is sending data cheaper than calculating locally?
- 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/
- 28. Does IoT make API design an afterthought?
- 29. • Informaton • Product • Service Business Asset • API • SLA • EULA API Provider • Building Thing Maker • Using API Thing • Using Thing End-User Effective API Design
Editor's Notes
- 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