Note: the project is under development and in alpha stage
elbus is a rust-native IPC broker, written in Rust/Tokio, inspired by zeromq and nanomsg. elbus is fast, flexible and very easy to use.
The library can be embedded in any Rust project or be used as a standalone server.
The project web site and documentation is available at https://elbus.bma.ai/ (under construction).
The following communication patterns are supported out-of-the-box:
The following channels are supported:
In addition to Rust, elbus has also bindings for the following languages:
Rust crate: https://crates.io/crates/elbus
A client should register with a name "group.subgroup.client" (subgroups are optional). The client's name can not start with dot (".", reserved for internal broker clients) if registered via IPC.
Broadcast messages are sent to multiple clients at once. Use "?" for any part of the path, "*" as the ending for wildcards. E.g.:
"?.test.*" - the message is be sent to clients "g1.test.client1", "g1.test.subgroup.client2" etc.
Use MQTT-format for topics: "+" for any part of the path, "#" as the ending for wildcards. E.g. a client, subscribed to "+/topic/#" receives publications sent to "x/topic/event", "x/topic/sub/event" etc.
An optional included RPC layer for one-to-one messaging can be used. The layer is similar to JSON RPC but is optimized for byte communications.
elbus has ZERO security model in favor of simplicity and speed.
See examples folder.
cargo build --features server,broker-api
The "broker-api" feature is optional. When enabled, it allows to call broker internal functions and call RPC procedures from the command line with fifo channels.
Bohemia Automation / Altertech is a group of companies with 15+ years of experience in the enterprise automation and industrial IoT. Our setups include power plants, factories and urban infrastructure. Largest of them have 1M+ sensors and controlled devices and the bar raises upper and upper every day.