why http won't work for the internet of things

Why HTTP Won’t Work For IoT

CONFIDENTIAL - 2lemetry, LLC

Tim Kellogg April 10, 2014@kellogh

John Rotach@rotach

Internet of Things

Internet of Things

Telemetry

Telemetry

BrokerPublish Cloud ConnectorsSubscribe

Enterprise Integrations

Subscribe

Devices

Sensors

HTTP is for request/response

HTTP

Client ServerRequest

Response

HTTP

MQTT

Quality of Service (QoS)

Topics

MQTT Features

MQTT-SN

MQTT-SN

Gateway

Broker

CoAP

Constrained Application Protocol

GET+Observe

Questions?

@kellogh

APPENDIX

CONFIDENTIAL - 2lemetry, LLC

We power the connected enterprise• 2lemetry is an IoT technology and solutions company

that powers the connected enterprise, tying people, processes, data and devices together—transforming raw data into real-time actionable intelligence.

• Founded 2011—spun off from hardware manufacturer

• 100% Focus on Internet of Things—with a “cloud first” focus

Technology - ThingFabric

Broker Layer

Data Storage

CEP EngineRules Engine

REST API

Regional Load Balancing

• Historical data storage• Automation replication• Schemaless

• Find trends• Run computations• Build complex models

• HTTP webhook• Republish rules• SMS/Email• Reformat payloads

• Supports custom protocols• Supports MQTT, Stomp, CoAP• Balanced by geographical response time

2lemetry technology, solutions, partners and expertise to provide an end to end solution

Technology2lemetry Device Cloud

Platform

SolutionsEnterprise system

integration tools

Digital signage

Proximity sensing

Facial recognition

PartnersAcross entire IoT project lifecycle

Sales channel

ExpertiseIoT strategy

Integration expertise and application development

Managed service and support

CONFIDENTIAL - 2lemetry, LLC