The Event Horizon -- Designing API's for the Internet of Things
summary
Claim: everything with an identity will expose an API and identity must carry context; practical IoT systems use publish–subscribe semantics, presence signals, and domain-local meshes that only occasionally propagate events to the cloud. Implementations at scale use WebSockets/Socket.IO, WebRTC data channels, XMPP for building-wide HVAC deployments, and lightweight protocols like MQTT/CoAP/STOMP with QoS levels (fire‑and‑forget, at‑least‑once, exactly‑once) and stacks measured in tens of kilobytes. Default to HTTP/REST until resource constraints force a switch.
AI-written summary · about
chapters (5)
- 0:00Start
- 3:53What Is the Internet of Things
- 13:58Multiplexing
- 16:50Web Rtc Data Channels
- 22:12Qualities of Service
related talks
24mConnecting the World/Cities with Events Flows and APIs Interactions.
29mAPIs and Event Streaming Dualty
30mThe internet of things challange:building APIs that last for decades
45mThe Changing Face of Communications: IoT, REST, & Reactive
20mAvoid the Silos and Help Build the True Internet of Things
39mThe Internet of Things in Practice
27mPatterns for Event-Driven APIs
32mNavigating Modern API Platforms: Insights & Strategies