IoTaConf 2014 - IoT Connectivity, Standards, and Architecture
•
3 j'aime•1,880 vues
Communication Patterns, Protocols, and Architecture in IoT.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (11)
Similaire à IoTaConf 2014 - IoT Connectivity, Standards, and Architecture
Similaire à IoTaConf 2014 - IoT Connectivity, Standards, and Architecture (20)
Dernier
Dernier (20)
IoTaConf 2014 - IoT Connectivity, Standards, and Architecture
- 1. IoT Connectivity, Standards & Architecture Todd L. Montgomery @toddlmontgomery IOTAConf! October 20-21, 2014!
- 2. Communication Patterns Lead to… Protocols (Standards?) Lead to… Architecture “Fear is the path to the dark side. Fear leads to anger. Anger leads to hate. Hate leads to suffering.” — Yoda
- 4. Request Response What most of us think happens
- 5. Request Response And that is… what really happens… but…
- 6. But… Who does this? Request Response What also really happens
- 7. Request Response @toddlmontgomery Support (UI/Device) Security (Challenge) Keep-Alive or Watchdog User State Query
- 8. News, Stocks, Texts/SMS, Video, Audio, Social, … Stream What also really happens
- 9. Temperature, Heart Rate, Web Logs, Sensor Data, Seismic Readings, Steps, Stairs, Gyro Data, GPS, Acceleration, Breathing, EKG, EEG, … Ingest What also really happens
- 10. Pretty much how everything actually works… Request Stream & Ingest Response What also really happens
- 11. What also REALLY happens
- 12. Request, Response, Stream, and Ingest are really types Message Message The Break Down Message-Driven Message-Driven
- 13. Message Driven Reactive Applications Elastic Responsive Resilient http://www.reactivemanifesto.org/
- 14. Meanwhile… IoT…
- 16. HTCPCP RFC 2324, Extended by RFC 7168 "there is a strong, dark, rich requirement for a protocol designed espressoly [sic] for the brewing of coffee" http://en.wikipedia.org/wiki/Hyper_Text_Coffee_Pot_Control_Protocol @toddlmontgomery
- 17. @toddlmontgomery
- 18. BREW 418 I’m a teapot WHEN "This has a serious purpose – it identifies many of the ways in which HTTP has been extended inappropriately.” — Larry Masinter, author http://larry.masinter.net/ @toddlmontgomery
- 20. courtesy of
- 21. Sometimes it is good to reinvent the wheel
- 22. What History Has Taught Us @toddlmontgomery
- 25. THE IoT Runtime!
- 26. THE IoT ______!
- 27. Internet of Things Multi-Lingual (and Polyglot) Multi-Protocol & Multi-Standard Multi-“Platform” Massive Scale Highly Integrated What is already is…
- 28. Connected. Integrated. Great time to be a protocol geek!
- 29. pro·to·col noun ˈprō-tə-ˌkȯl, -ˌkōl, -ˌkäl, -kəl @toddlmontgomery ! ... ! 3 b : a set of conventions governing the treatment and especially the formatting of data in an electronic communications system <network protocols> ... 3 a : a code prescribing strict adherence to correct etiquette and precedence (as in diplomatic exchange and in the military services) <a breach of protocol> !
- 30. Protocols are the key to Integration REST has demonstrated this! @toddlmontgomery
- 31. Protocols & Standards @toddlmontgomery
- 32. Binary Encoding helps save CPU & Bandwidth! Persistent connections help a LOT! (fewer frames) Well designed protocols help a LOT MORE! Battery Life Many simultaneous connections hurt! Using the wrong protocol with the wrong pattern hurts A LOT! @toddlmontgomery Stay out of High Energy State! One reason why we should care about Protocols… ASCII Encoding hurts CPU & Bandwidth!
- 33. HTTP RFC 2068, 2616, …, 7230-7240 Request Response Synchronous Request/Response @toddlmontgomery Bi-Directional… kinda, but… Event Event June 2014 … only one direction at-a-time
- 34. http://en.wikipedia.org/wiki/List_of_web_service_specifications Request ACK Response ACK @toddlmontgomery Sync Request Sync Response Web Services … Event Event But… Async Request/Response… kinda No, seriously, lots of these!!
- 35. HTTP Upgrade 101 Switch Events Events @toddlmontgomery Async Request/ Response Really a Transport Protocol Streaming WebSocket RFC 6455 Full Duplex, Asynchronous “TCP over the Web” Ingest https://tools.ietf.org/html/rfc6455
- 36. Events Events @toddlmontgomery Async Request Async Response SPDY & HTTP/2 IETF Drafts Async Request/Response Multiple Streams Efficient Headers (HPACK) Binary Encoding http://www.ietf.org/id/draft-ietf-httpbis-http2-14.txt
- 37. There is emerging implementation experience and interest in a protocol that retains the semantics of HTTP without the legacy of HTTP/1.x message framing and syntax, which have been identified as hampering performance and encouraging misuse of the underlying transport. — IETF httpbis Charter http://datatracker.ietf.org/wg/httpbis/charter/
- 38. Events Events @toddlmontgomery Async Request Async Response WebSocket over HTTP/2 IETF Draft Streaming Ingest Full Duplex, Asynchronous with Multiple Channels/Streams http://www.ietf.org/id/draft-hirano-httpbis-websocket-over-http2-01.txt
- 39. Runs over TCP or WebSocket (v3.1.1) Broker-Based MQ Telemetry Transport (MQTT) @toddlmontgomery http://mqtt.org/ Lightweight Publish/Subscribe Messaging Transport MQTT-SN for non-TCP/IP OASIS Standard
- 40. Constrained Application Protocol (CoAP) IETF CoRE WG (Constrained RESTful Environments) @toddlmontgomery https://tools.ietf.org/html/rfc7252 Runs over UDP, DTLS, or WebSocket Request/Response (either direction), Publish/Subscribe Standardized HTTP Mapping Resource Discovery, Linking, etc. RFC 7252
- 41. Extensible Messaging & Presence Protocol (XMPP) @toddlmontgomery https://tools.ietf.org/html/rfc6120 Brokered TCP + TLS + SASL Presence & Persistent Streams XMPP Standards Foundation (Semi) Structured XML IETF RFC 6120 (obsoletes 3920)
- 42. XMPP HTTP/1.1 Protocols? Shared Memory IPC CoAP AMQP WebSocket JMS WebRTC Not just in the traditional sense… MQTT HTTP/2 TCP/UDP/IP Aeron 0MQ DDS
- 44. Micro-Services Architectures http://martinfowler.com/articles/microservices.html @toddlmontgomery
- 45. Rx Languages Erlang & Elixir Go And Frameworks RxJS RxJava Akka Streams Akka Rust
- 46. @toddlmontgomery Client? Device? Browser? Back-End? DMZ? Protocols Protocols Protocols
- 48. Protocols Deployment Container Nuklei Logic Reactive Message Stream Depends on language, runtime, platform, etc. Asynchronous Binary “Loose” Ordering Client? Server? Browser? Device? ALL!
- 49. Choice of protocols becomes deployment concern Protocols Deployment Container Nuklei Logic Reactive Message Stream Consistent ABI Various Protocol Options Asynchronous Binary Boundary
- 50. Message Message To Sum Up Message-Driven Message-Driven
- 51. @toddlmontgomery Questions? • Kaazing http://www.kaazing.com • GitHub https://github.com/kaazing • Reactive Manifesto http://www.reactivemanifesto.com • SlideShare http://www.slideshare.com/toddleemontgomery • Twitter @toddlmontgomery Thank You!