The Internet of Things (IoT) is topping the charts for buzzword appearances on technology hot lists. What is this magical term? Maybe you've already connected physical devices to your computer. That's awesome! This is only the beginning. IoT is more than just controlling mad robots with your new laptop. Learn how the Zetta project (http://www.zettajs.org) enables you to take your existing JavaScript skills and power a massively distributed system of physical devices. Model devices as state machines. Inspect the reactive hypermedia API Zetta produces. Wire up interactions between physical devices from across the globe. IoT is more than just a bad acronym. Learn how you can start your own Internet of Things project today!

1. Using JavaScript to Put
the “Internet” in IoT
@kevinswiber

2. Open source platform for
the Internet of Things
http://zettajs.org

3. Internet of Things

4. Ubiquitous Computing

5. Like control systems
Sensor Actuator
Controller
Environment
The Internet
…but on the Internet

6. More than 50B connected
devices by 2020

7. 99 Problems

8. Technology

9. Coordination

10. Analysis

11. Experience

12. Decisions

13. Protocols
• HTTP/1.1
• WebSockets
• SPDY
• Future: HTTP/2

14. Crossing Network
Boundaries
• Access
• Interaction
• Streaming

15. Why Node?
• Evented, async
• Open Source
• Cross-platform
• Because you know
JavaScript!

16. Nuts & Bolts

17. Reaching the Edge
DevicesDevicesDevices
Zetta
Zetta
DevicesDevicesDevices
Zetta
ClientsClientsClients
ClientsClientsClients Private Network
Data Center
Internet

18. Desired Architectural
Properties
• Decoupling of implementations
• Independent evolution
• Scale
• Load balancing
• Centralize complexity, distribute simplicity
• Reduce latency
• Support event streams

19. Architectural Constraints
• Client-server, stateless, cacheable, layered
system, uniform interface, etc.
Wait, isn’t that REST?

20. The hypest of all media!
http://sirenspec.org

21. What about event streams?

22. How streams are done over
HTTP today
• WebHooks
• Chunked Transfer-Encoding
• HTTP Pipelining
• Long Polling
• Server Sent Events
X
X
X
X
X

23. Just upgrade

24. Zetta Process
Zetta Components
Scouts Drivers
Apps
create
observe

25. Model drivers as finite state
machines
LED.prototype.init = function(config) {
config
.type('led')
.state('off')
.when('off', { allow: ['turn-on'] })
.when('on', { allow: ['turn-off'] })
.map('turn-on', this.turnOn)
.map('turn-off', this.turnOff);
};

26. Transitions are represented
as affordances in the API.
"actions": [
{
"name": "turn-on",
"method": "POST",
"href": “...”,
"fields": [
{
"name": "action",
"type": "hidden",
"value": "turn-on"
}
]
}
]

27. We need to consume an
object stream.
links: [
{
title: “pulse“,
rel: [“http://rels.zettajs.io/object-stream“],
href: “ws://...”
}
]

28. We need to consume an
object stream.
» wscat -c ws://...
connected (press CTRL+C to quit)
< {"topic":"heartbeat/1/pulse","timestamp":1411757412119,"data":61}
< {"topic":"heartbeat/1/pulse","timestamp":1411757412620,"data":65}
< {"topic":"heartbeat/1/pulse","timestamp":1411757413121,"data":69}
< {"topic":"heartbeat/1/pulse","timestamp":1411757413622,"data":71}
< {"topic":"heartbeat/1/pulse","timestamp":1411757414124,"data":66}
< {"topic":"heartbeat/1/pulse","timestamp":1411757414626,"data":64}
< {"topic":"heartbeat/1/pulse","timestamp":1411757415128,"data":68}
< {"topic":"heartbeat/1/pulse","timestamp":1411757415629,"data":63}
< {"topic":"heartbeat/1/pulse","timestamp":1411757416130,"data":65}
< {"topic":"heartbeat/1/pulse","timestamp":1411757416631,"data":63}

29. Monitor resource events
before taking action.
links: [
{
title: “logs“,
rel: [
“monitor“,
“http://rels.zettajs.io/object-stream“
],
href: “ws://...”
}
]

30. Monitor resource events
before taking action.
» wscat -c ws://...
connected (press CTRL+C to quit)
< {"topic":"led/2/logs","timestamp":
1411809676901,"transition":"turn-on","input":[],"properties":
{"id":"2","type":"led","name":null,"state":"on"}}
< {"topic":"led/2/logs","timestamp":
1411809677548,"transition":"turn-off","input":[],"properties":
{"id":"2","type":"led","name":null,"state":"off"}}
< {"topic":"led/2/logs","timestamp":
1411809678483,"transition":"turn-on","input":[],"properties":
{"id":"2","type":"led","name":null,"state":"on"}}
< {"topic":"led/2/logs","timestamp":
1411809679126,"transition":"turn-off","input":[],"properties":
{"id":"2","type":"led","name":null,"state":"off"}}

31. We also need binary.
links: [
{
rel: [“http://rels.zettajs.io/binary-stream“],
href: “ws://...“,
type: “video/mpeg“,
}
]

32. We also need binary.
» wscat -c ws://...
connected (press CTRL+C to quit)
Q`rCEDˌDIp=`"3ss79:Yk}{` 5e`>9%J[K89z^> 8X Gp;W̮qXF
h1{%O;7<Bi‫.ڞ‬r r5
vyeK[X@ƯDRmT:uLz[‫ޱްޯޮޭެޫުީިާަޥޤޣޢޡޠޟޞޝޜޛޚޙޘޗޖޕޔޓޒޑސޏގލތދފމވއކޅބރނށހ‬V
.vK",,u!N8֝=LQ=s~ӆ`]{E6[
WȝM]3Uo|&n
Њmo('/K>2칩e,l{%`:<rtN|SXu曆psFJS*s#AB]ý0Rt_`uS}vX3ctA>kJfuΎ^L๖䜼V"u8GU
‫*ڹ‬

33. We also need binary.
» wscat -c ws://...
connected (press CTRL+C to quit)

34. Reactive Clients
var siren = require('siren');
!
siren()
.load('http://zetta-cloud-2.herokuapp.com')
.link('http://rels.zettajs.io/peer', 'Detroit')
.entity(function(e) {
return e.properties.type === 'sound';
})
.link('http://rels.zettajs.io/object-stream', 'level')
.monitor()
.subscribe(console.log);

35. Reactive Clients
var zrx = require('zrx');
!
zrx()
.load('http://zetta-cloud-2.herokuapp.com')
.server('Detroit')
.device(function(d) {
return d.type === 'sound';
})
.stream('level')
.subscribe(console.log);

36. It works!

37. Going Forward

38. Solve the producer-
consumer problem.

39. Reactive Stream Control
Protocol
• Consumer controlled streams
• Runs over WebSockets
• Multiplex streams
• URI scheme definition
• Will be supported on HTTP/2 + WebSockets.

40. What can you do with
streams?
• Monitoring values over time
• Distributed data processing
• Event sourcing
• Batches

41. // TODO:
• Extract reactive hypermedia framework from
Zetta internals.
• Produce a clean specification and
documentation.
• Experiment with multiple languages/platform
implementations.

42. Hit me up!
• kswiber@gmail.com
• https://twitter.com/kevinswiber
• https://linkedin.com/in/kevinswiber
• https://github.com/kevinswiber