ReactOBus is a message broker that helps to create software bus over the network and to react to some messages.

ReactOBus is able to:

• collect events (as network messages) from different sources
• publish the stream of events
• store the events in a database
• launch specific commands when an event match some conditions

In a near future, ReactOBus will be able to:

• filter-out some events
• modify on-the-fly event format
• ...

ReactOBus is known to work with Python3.4 and Python3.5 under Linux.

It depends on (see requirements.txt):

• pyzmq
• pyYAML
• SQLAlchemy (if you wish to store events in a database)
• setproctitle

Executing ReactOBus directly from the sources:

git clone https://github.com/ivoire/ReactOBus.git
cd ReactOBus
virtualenv -p python3.5 venv
source venv/bin/activate
pip install -r requirements.txt
python reactobus.py --level DEBUG --conf share/examples/reactobus.yaml

The configuration file is a YAML dictionnary with:

• inputs: a list of input streams
• outputs: a list of output streams
• core: configuration of the internal sockets
• reactor: the reacting part of ReactOBus
• db: the database configuration

All keys except core and inputs are optional. If the optional keys are not found in the configuration, the corresponding modules won't be loaded.

For the moment, ReactOBus only accepts one type of messages. The messages should be multipart ZMQ messages with the folowing meaning:

• topic
• uuid (as generated by uuid.uuid1() in Python)
• datetime when the message was generated (isoformat)
• username of the sending process or user
• data as JSON