Public | Automated Build

Last pushed: 3 days ago
Short Description
IoT bridge biot, tuned for running in swarm or CoreOS cluster
Full Description

Introduction

Biot is a network-aware information pipe for the IoT. Biot stands for
"Bridge for the Internet of Things", it aims at easily bridging
together the various APIs that are involved in IoT projects. Simply
put biot accepts a number of sources, acquires data from these
sources, extracts any number of variables from this data and pushes
templates using these variables to any number of destinations. In
other words, biot is an easy API masher for the Internet of Things.

biot supports a wide number of source and destinations types and
makes the difference between those using URL schemes. For example,
biot implements file and exec to receive or send data from and to local
files and external programs. In addition, biot supports schemes such as
http (encrypted and clear text HTTP), ws (encrypted and clear text
WebSockets), stomp, xmpp, syslog. All these schemes are flexible
enough to, through options and sugaring, access remote services through
REST-like vocabularies or initiate topic subscriptions within WebSockets
protocols.

Biot is tuned to work in modern cloud architectures through its
ability to be made available as a docker component. Further, you
can easily instantiate as many biot information processing pipes in a
cluster using fleet (and CoreOS). In this context, biot is
for example able to acquire its data from the etcd key-value store and
process data as instructed. This is achieved through the implementation
of an etcd URL scheme on top of the etcd-tcl library and the ability
for biot to acquire its command-line parameters using the etcdscheme
(or more regular http accesses).

For more details, consult the Wiki.

Docker Pull Command
Owner
efrecon
Source Repository

Comments (0)