ELBUS - Rust-native IPC broker
What is ELBUS
The library can be embedded in any Rust project or be used as a standalone server.
NOTE: ELBUS is not officially released yet and SDK can be changed at any time without any backward compatibility. ELBUS (stands actually for "EVA ICS Local Bus") is the key component of EVA ICS v4, which is going to be released in 2022-2023.
The name "ELBUS" is also only the working one, after the official release the bus will be renamed, as well as its crates, bindings and modules.
Available at https://elbus.readthedocs.io/
The following communication patterns are supported out-of-the-box:
- one-to-one messages
- one-to-many messages
The following channels are supported:
- async channels between threads/futures (Rust only)
- UNIX sockets (local machine)
- TCP sockets
In addition to Rust, ELBUS has also bindings for the following languages:
- Python (sync): https://pypi.org/project/elbus/
- Python (async): https://pypi.org/project/elbus-async/
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.
The client's name must be unique, otherwise the broker refuses the registration.
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.
Security and reliability model
ELBUS has a very simple optional security model in favor of simplicity and speed. Also, ELBUS is not designed to work via unstable connections, all clients should be connected either from the local machine or using high-speed reliable local network communications.
If you need a pub/sub server for a wide area network, try PSRT.
See examples folder.
Build a stand-alone server
cargo build --features server,rpc
The "rpc" feature is optional. When enabled for the server, it allows to initialize the default broker RPC API, spawn fifo servers, send broker announcements etc.
Broker: 4 workers, clients: 8, payload size: 100 bytes, local IPC (single unix socket), totals:
About the authors
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 higher and higher every day.