The internet of things challange:building APIs that last for decades
summary
Claim: APIs must use hypermedia and explicit media types so clients don’t hardcode URLs and break when servers change. Backed by Cisco’s projection of 50 billion devices and the web’s 25‑year durability, the prescription includes a seven‑step design (identify resources, draw state machines, reconcile names), use of media types like UBER with profiles (ALPS, XMDP) for domain semantics, and real deployments (AWS streaming, Elastic Path, Comcast, PayPal) that demonstrate clients can evolve with servers.
AI-written summary · about
chapters (8)
- 0:00The importance of durable APIs
- 1:34Software vs. civil engineering
- 5:21Learning from the web
- 9:44Decoupling with hypermedia
- 12:34Affordances and familiarity
- 16:51Solving the semantic gap
- 22:13A practical design process
- 28:37Adoption and resources
related talks
35mBuilding Your API for Longevity
43mThe Hypermedia API
28mDesigning Hypermedia APIs
49mSurviving the Zombie Apocalypse of Connected Devices
01h 02mHypermedia and the Rest of REST
17mFuture-Proof by Design: Building IoT Solutions that Endure
43mHow the Web Evolves with Hypermedia
58mHypermedia APIs and the Future of AI Agentic Systems