Repository navigation
ringfire 0.5.0
Network mirrors: a ring on one host, identical copies with the same sequence numbers on others.
ringfire serve/ringfire mirrorand thereplicationmodule (ReplicaServer,Mirror,MulticastConfig): records travel as raw slot bytes, so one pair works for any element type;BlobProducerrings (variable-length payloads) are mirrored too.- Three transports: TCP; UDP multicast (one datagram for every mirror on a LAN); UDP unicast with NAT punching for other sites and clouds, with
--dup Nto send every datagram N times. Lost datagrams are recovered from the source ring over TCP (NAK/GAP); a mirror is written strictly in sequence order, never reordered or duplicated. - A mirror can be served again, so one copy per site crosses the WAN and a hub redistributes locally.
FLAG_SPARSE(0x0400): readers on mirror rings skip holes instead of waiting on them.- Frame pacing (
--linger-us, adaptive by default) keeps the datagram rate near 20k/s under load. - Measured: 30 µs push-to-read across a 1 GbE LAN to each of six mirrors; 16 mirrors at p99 72 µs over multicast; 0 lost / 0 reordered from 1k to 1M msg/s; Tokyo → Los Angeles UDP p99 50 µs above its median where TCP pays a full extra round trip for 1 record in 100. Details, diagrams and recipes: docs/replication.md.
Full changelog: CHANGELOG.md.