In the ”Internet of Things” (IoT) vision the physical world blends with virtual one, while machine-to-machine interaction improve our daily life. Clearly, how these virtual objects are exposed to us is critical, so that their user interface must be designed to support the easiness of usage that is driven by the users’ needs, which is different from what machines requires. These two requirements must be solved, and an integrated solution should emerge, if we want to bring the IoT to the 50 billions network that is predicted to became in the next years.
39. • MQTT broker
• REST interface
• can be deployed on
top of very pub/sub
systems
• built in node.js
QEST
REST Server
Redis
MQTT Server
QEST
Data Layer
HTTP Clients MQTT Clients
40. • Ascoltatori: the pub/sub library for node backed by
Redis, MongoDB,AMQP (RabbitMQ), ZeroMQ, MQTT
(Mosquitto) or just plain node: https://github.com/
mcollina/ascoltatori
• Mosca, the multi-transport MQTT broker for node.js.
It supports AMQP, Redis, ZeroMQ or just MQTT:
https://github.com/mcollina/mosca
• MQTT.js, the MQTT library for node: https://
github.com/adamvr/MQTT.js
QEST’s pillars
46. There are LOTs
of choices
Developers think in Lists
and Maps, not in nodes
and children.
XML will not play a major
role in the Internet of
Things
47. • What devices can a user monitor?
• What devices can 'listen' to the state of
other devices?
• Who can access the devices state?
• Is the communication secure?
Security Issues