the web of things
TRANSCRIPT
The Web of Things WoT Now
@frankgreco
Background
§ Director of Technology @ Kaazing § Chairman NYJavaSIG (javasig.com) § Largest Java UG in North America
8,000+ members § [email protected], @frankgreco § Principal Evangelist - Kaazing § [email protected], @krhoyt § “IoT and the New Web”
5pm today N-121
Everyone wants to play in the IoT game
History
History
A Primary Tenet of Computing
If History Repeats Itself, Is There No Future?
u Internet – Global system of interconnected networks that use IP to communicate
u 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…
u A popular application service on the Internet
u Based on TCP/IP
u 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
u Two major protocols
HTTP (1988/1999) and WebSocket (2007/2011)
The Web
u A riff on “Ubiquitous Computing” (“Pervasive”)
• Mark Weisner PARC 1988
u Its early so there’s different definitions
• Similar to early days of Cloud Computing
u M2M has been around for decades.
• Primarily proprietary embedded systems and typically point-to-point (RPC)
u IoT/IIoT (Industrial IoT)
• Adds Internet connectivity
• Networks of M2M systems connected via IP
Now… IoT, IIoT and M2M
u No formal API standards
u Many protocol standards – interoperability low
u No common, wide-reaching frameworks
u No composition possibilities
u Difficult to leverage economies of scale
u Barrier to entry is high for millions of app developers
u M2M/IIoT is foreign to most app developers
u Also… we’re in a connected world now cloud, mobile, web APIs
IoT/IIoT – Connectivity isn’t Sufficient
u IoT – Internet of Things • Embedded computing endowed with Internet connectivity
u WoT – Web of Things • Application and Services layer over IoT
u Apply the benefits of the Web to IoT u WoT is a uniform interface to access IoT functionality
u Provides the abstraction for control/monitoring (sensors/actuators)
u Accelerates innovation u Deployment, development, interoperability, economy of
scale… u Why is this important?... Evolution
Here’s Where the Web Comes In
The Hidden Web – Most of the Web is Not Visible
http://thumbs.dreamstime.com/x/iceberg-23503494.jpg
browsers
APIs
Services
$2B API Revenue
Analytics / CEP
Developers!
The Web of Things is all about IoT SERVICES!
Monitoring / Management
Persistence Engine
Services
Security
Connectivity
Internet of
Documents
Internet of
Services
u Disadvantages of HTTP Request/Response u Lack of resiliency and robustness u Enterprise events retrieved by resource intensive polling
techniques • Much bandwidth is wasted • Information can be delayed
u Composite services brittle and lack transactionality u Enterprises learned advantages of ESB 10+ years ago u See failures of CORBA, Sun RPC, etc. u Clumsy AJAX/Comet workarounds to simulate real-time
But Is HTTP the Right Choice for Every Service?
There are TWO Web Protocols
Request-Response, Synchronous
Event-based, Asynchronous
WebSocket
Risk Management
Big Data
The World is Naturally Event-based (“real-time”)
Logistics Music Presentation
Communication
Health Monitoring
Home Security
Remote Control
Local Transportation
Intelligent Appliances
Monitoring and Management
u Designed for document transfer – HTTP
ü Short-lived Request / Response interaction
u Bidirectional, but half-duplex
ü Traffic flows in only one direction at a time
u Stateless
ü Large amounts of metadata resent for each request
The Web was not originally designed for “real-time”, event-based services…
Legacy Web
u IETF Protocol and W3C JavaScript API for real-time, bi-directional, always-on connections
u RFC 6455 – Dec 2011
u Easily add event-based data to web apps ü ws://mycompany.com/collaboration_svc
ü wss://anothercompany.com/marketdata
u Avoids polling
u Avoids HTTP meta-data overhead
u Shares port with HTTP (80/443)
u Traverses Firewalls
WebSocket – “TCP for the Web”
WebSocket
TCP/IP
JMS XMPP AMQP B2B FTP VNC MQTT etc
Browser and Native Applications
WebSocket Gateway
Internet
WebSocket Gateway
Protocol Layering is Possible
WebSocket is a Transport
layer!
svc svc svc svc svc svc
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
Data Flow – Human Web vs WoT
Do human-readable protocols make sense for non-humans?
GW
GW
GW
IoT/IIoT
WoT
WoT
WoT
Event Gateway Architecture
GW
GW
GW
GW
GW
GW
GW
Aggregator nodes
• Scalability • Querying • Performance • Manageability • Composition • Circles of Trust • Event processing • CDN++
Event Gateway Architecture – Future Directions
“…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
The Message is the Medium
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?
History Repeats Itself…
Web of Things
http://www.w3.org/2014/02/wot/
Click to Edit Master Title Style
Demos
Thank You!
@frankgreco