BUS/RT® is a Rust-native IPC broker, written in Rust/Tokio, inspired by NATS, ZeroMQ and Nanomsg. BUS/RT is fast, flexible and very easy to use, optimized for both high-load and ultra-low latency real-time scenarios.
The library can be embedded in any Rust project or be used as a standalone server.
BUS/RT is the core bus of EVA ICS v4.
The following communication patterns are supported out-of-the-box:
- one-to-one messages
- one-to-many messages
- pub/sub
The following channels are supported:
- async channels between threads/futures (Rust only)
- UNIX sockets (local machine, Linux/BSD)
- TCP sockets (Linux/BSD/Windows)
In addition to Rust, BUS/RT has also bindings for the following languages:
- Python (sync): https://pypi.org/project/busrt/
- Python (async): https://pypi.org/project/busrt-async/
- JavaScript (Node.js): https://www.npmjs.com/package/busrt
- Dart https://github.com/AndreiLosev/busrt_client
Rust crate: https://crates.io/crates/busrt
Use rt
feature to use for internal mutexes
parking_lot_rt
- a parking_lot
fork without spin-locks, which is real-time safe.
The full documentation is available at: https://info.bma.ai/en/actual/busrt/
CPU: i7-7700HQ
Broker: 4 workers, clients: 8, payload size: 100 bytes, local IPC (single unix socket), totals:
stage | iters/s |
---|---|
rpc.call | 126_824 |
rpc.call+handle | 64_694 |
rpc.call0 | 178_505 |
send+recv.qos.no | 1_667_131 |
send+recv.qos.processed | 147_812 |
send.qos.no | 2_748_870 |
send.qos.processed | 183_795 |
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.