This document discusses the Web of Things (WoT) and how it can provide a uniform interface to access functionality from the Internet of Things (IoT). The WoT applies concepts from the Web, such as standardized APIs and protocols like HTTP and WebSocket, to accelerate innovation in the IoT space. WebSocket in particular provides full-duplex communication capabilities that are more suitable for real-time event-driven communication compared to HTTP request/response. The document also presents architectures for event gateways that can connect IoT devices and scale to support large numbers of devices and data flows.

1. The Web of Things
WoT Now?
Frank Greco
Director of Technology
frank.greco@kaazing.com

2. © 2014 Kaazing Corporation. All Rights Reserved.
Speakers
Peter Moskovits
Head of Real-Time Solutions
peter.moskovits@kaazing.com
@pmoskovi
Frank Greco
Director of Technology
frank.greco@kaazing.com
@frankgreco

3. © 2014 Kaazing Corporation. All Rights Reserved.
§ Internet – Global system of interconnected networks that
use IP to communicate
§ Internetworking – Connecting one network with another
through a series of Gateways that provide a common
method of communication
Let’s take 1 step back to go 2 steps ahead…

4. © 2014 Kaazing Corporation. All Rights Reserved.
§ A popular application service on the Internet
§ Based on TCP/IP
§ Advantages
§ Application deployment simplified – URI
§ Interoperable open standards and specifications
§ Ease of programmability – scripting
§ Global reach and Economy of scale
§ Accessed by ubiquitous Browsers and also non-Browsers
§ Two major protocols
- HTTP (1988/1999) and WebSocket (2007/2011)
The Web

5. © 2014 Kaazing Corporation. All Rights Reserved.
§ A riff on “Ubiquitous Computing” (also “Pervasive”)
- Mark Weisner PARC 1988
§ Its early so there’s different definitions
- similar to early days of Cloud Computing
§ M2M has been around for decades. Primarily proprietary
embedded systems and typically point-to-point (RPC)
§ IoT/IIoT (Industrial IoT)
- Adds Internet connectivity
- Networks of M2M systems connected via IP
Now… IoT, IIoT and M2M

6. © 2014 Kaazing Corporation. All Rights Reserved.
§ No formal API standards
§ Many protocol standards – interoperability low
§ No common, wide-reaching frameworks
§ No composition possibilities
§ Difficult to leverage economies of scale
§ Barrier to entry is high for millions of app developers
§ Also… we’re in a cloud, mobile, web api world
IoT/IIoT – connectivity isn’t sufficient

7. © 2014 Kaazing Corporation. All Rights Reserved.
§ IoT – Internet of Things
- Embedded computing endowed with Internet connectivity
§ WoT – Web of Things
- Application and Services layer over IoT
§ Apply the benefits of the Web to IoT
§ WoT is a uniform interface to access IoT functionality
§ Provides the abstraction for control/monitoring
§ Accelerates innovation
Here’s where the Web comes in
IoT
WoT
Developers!

8. © 2014 Kaazing Corporation. All Rights Reserved.
Higher Level APIs Reduces Complexity
Simplicity is a
Useful
Abstraction!
Simplicity enables
Innovation
Complexity
Innovation

9. © 2014 Kaazing Corporation. All Rights Reserved.
But Is HTTP the Right Choice?
9
l Disadvantages of HTTP Request/Response
l Lack of resiliency and robustness
l Enterprise events retrieved by resource intensive polling
techniques
u Much bandwidth is wasted
u Information can be delayed
l Composite services brittle and lack transactionality
l Enterprises learned advantages of ESB 10+ years ago
l See failures of CORBA, Sun RPC, etc.
l Clumsy AJAX/Comet workarounds to simulate real-time

10. © 2014 Kaazing Corporation. All Rights Reserved.
10
Legacy HTTP vs WebSocket
For Event-based Web Communication…
http:// ws://

11. © 2014 Kaazing Corporation. All Rights Reserved.
WebSocket
§ Includes W3C API and IETF Protocol (RFC 6455)
- Event-driven JavaScript API
- Full-duplex communication protocol
§ Integrates HTTP addressing
- ws://yourcompany.com/collaboration_svc
- wss://anothercompany.com/marketdata_svc
§ Traverses firewalls, proxies, routers securely
§ Text and Binary
§ Application-level Socket over the Web

12. © 2014 Kaazing Corporation. All Rights Reserved.
WebSocket
TCP/IP
JMS XMPP AMQP B2B FTP VNC MQTT etc
Browser and Native Applications
WebSocket
Gateway
Internet
WebSocket
Gateway
Protocol Layering is Possible

13. © 2014 Kaazing Corporation. All Rights Reserved.
History Repeats Itself
RPC
Asynchronous
RPC
Messaging
Enterprise Web/WoT
REST
Asynchronous
REST
Messaging
• Can wait for response
• Tight coupling
• Centralized business
processes
• Vertical interaction
• Easy to understand (xact)
• Future response
• Loose coupling
• Independent business
processes
• More complexity (xact)
Did I mention History repeats itself?...
ESB ISB

14. © 2014 Kaazing Corporation. All Rights Reserved.
The Message is the Medium
“…terse, self-classified
messages, networking overhead
isolated to a specialized tier of
devices, and publish/subscribe
relationships are the only way to
fully distill the power of the
coming Internet of Things” –
Francis daCosta

15. © 2014 Kaazing Corporation. All Rights Reserved.
Data flow – Human Web vs WoT
Typically an App
Server and DB
App Server is
probably not the
right architecture
Human
Web
WoT
Large data to client
Small data to server

16. © 2014 Kaazing Corporation. All Rights Reserved.
Event Gateway Architecture
GW
GW
GW
IoT/IIoT
WoT
WoT
WoT

17. © 2014 Kaazing Corporation. All Rights Reserved.
Event Gateway Architecture – Future Directions
GW
GW
GW
GW
GW
GW
GW
Aggregator nodes
• Scalability
• Querying
• Performance
• Manageability
• Composition
• Circles of Trust
• CDN-like

18. © 2014 Kaazing Corporation. All Rights Reserved.
Click to Edit Master Title Style
Demos

19. © 2014 Kaazing Corporation. All Rights Reserved.
Raspberry Pi
Image source: http://www.oracle.com/technetwork/articles/java/raspberrypi-1704896.html

20. © 2014 Kaazing Corporation. All Rights Reserved.
Demo Setup

21. © 2014 Kaazing Corporation. All Rights Reserved.
The Web Bridges Continents
21

22. © 2014 Kaazing Corporation. All Rights Reserved.
Thank You!