The Changing Face of Communications: IoT, REST, & Reactive
summary
Forecasts show tens of billions of devices and a modest 1% share still creates roughly 50 million updates/sec and ~74.5 Gbps, so protocol choice matters for scale and latency. HTTP stays synchronous and chatty; WebSocket uses an HTTP Upgrade/101 handshake to become a full‑duplex framed transport with browser masking; HTTP/2 adds HTTP/2 multiplexing and HPACK header compression; CoAP (RFC 7252) runs CoAP over UDP for constrained, lossy networks; MQTT and XMPP fill pub/sub and presence roles. Choose by communication pattern—streaming, ingest, or request/response.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 1:05Internet of Things overview
- 6:47Reactive systems and change
- 10:38Protocols and etiquette
- 12:03HTTP evolution and REST
- 16:20WebSocket and protocol extension
- 23:26HTTP/2 and performance
- 29:27CoAP for constrained networks
- 33:18MQTT and XMPP for IoT
- 36:54Protocol selection and impact
- 39:43Q&A and closing
related talks
53mComparing Messaging Techniques for the IoT
33mThe Event Horizon -- Designing API's for the Internet of Things
59mIt's not your parents' HTTP
01h 01mThe Unsung Hero of Modern Software: Asynchronous Messaging
30mThe Messaging of Things
01h 00mHTTP/2 - The future of the web today
43mHTTP 2.0: why and how
01h 25mIntro + Deep Dive: Specialized Network Protocols for IoT+Edge with Kubernetes