IOTDB: Transporters

This is getting into a more esoteric topic, but once you buy into the
concept of ( Thing ID + Bands + JSON Dictionary ), you can do a lot of
operation very easily.

One idea we've started using extensively is the Transporter, docs here
https://github.com/dpjanes/iotdb-homestar/blob/master/docs/transports.md

Basically, a Transporter moves JSON data organized by (ID, Band) around
between different systems.

So for example, we have a Transporter for IOTDB. When we connect it to a
Transporter for Express, we have a JSON API in a couple of lines of codes.
If we connect it to a MQTT Transporter, we have notifications (and
potentially a complete MQTT driven system). Note that this isn't
theoretical: this is how the HomeStar project does its API.

If we connect it to a Database or a Filesystem Transporter, we have
persistence. If we connect to a Firebase Transporter, we have cloud
services.

Let's say you want to store a pile of sensor data. You simply make a
Transporter for your data store (say, Xively or Phant) and connect into an
IOTDB Transporter. All your data gets persisted magically.

All of these get implemented in a couple of lines of binding code.

D.