ringfire
Shared-memory interprocess rings with network multicast and unicast replication.
The problem
Local processes and independent workers may need to read an ordered stream from a shared-memory ring. ringfire provides Linux shared-memory rings and optional network replication with explicit gap handling.
Example uses
01. Local feed consumers
A local feed handler can publish records for separate consumer processes.
02. LAN mirrors
LAN mirrors can give independent workers their own local streams.
03. Ordered remote mirror
A remote mirror can preserve order while handling reported gaps explicitly.
Where it fits
ringfire copies payloads into and out of ring slots. Lossy and lossless modes have different producer behavior, and the ring is not a durable broker or event log.
Get started
Use the README and library examples for the CLI and replication setup.
Authoritative installation steps, architecture diagrams, and full configuration references are maintained in the repository:
Read the ringfire README on GitHub →
Limitations
- Requires Linux shared memory.
- Multicast depends on network support.
- Retention is bounded by ring capacity.
- Slow readers and mirrors can see gaps.
Cite this software
Alexander Panasenko (2026). ringfire: Shared-memory interprocess rings with network replication (archive 0.5.3+licenses.462b66d). Zenodo. https://doi.org/10.5281/zenodo.23028631This Zenodo archive is source snapshot 0.5.3+licenses.462b66d, based on v0.5.3 with MIT and Apache legal notices added. It is not a separate tagged release.
