Shared-memory IPC · TCP broker routing · Zig core

Low-latency messaging for clustered services.

RingLoom is a broker and service runtime for predictable service-to-service communication. Same-host services use memory-mapped ring buffers, while brokers route cross-host traffic over framed TCP.

Start with the docs Read architecture reference

Zero-copy local path Dedicated event loops Apache-2.0

Services IPC rings

Broker Control · Send · Receive

Peer brokers Framed TCP

Design skeleton

Website components are in place.

The final documentation and marketing copy can now be filled in section-by-section. These cards sketch the RingLoom story without locking in final wording.

↯

Predictable hot path

Local messages flow through pre-allocated shared-memory ring buffers, keeping syscalls and heap allocation away from the fast path.

◎

Brokered cluster routing

Messages are routed by node and service identifiers, with broker event loops dedicated to control, sending, and receiving.

▣

Reference-first docs

The website mounts engineering documents from the RingLoom repository into the reference section, so source docs stay canonical.

Documentation map

Usage docs, stack overview, and source reference.

Marketing pages and guided usage documentation live in this site. Deeper implementation notes are mounted from the RingLoom source tree.

Usage documentationQuickstart, concepts, operations, and examples. RingLoom stackBroker, service runtime, TCP transport, and bindings. Engineering referenceMounted from ../ringloom/docs.

Under Construction

This section is part of the design skeleton. Final copy, diagrams, examples, and API details will be added as the RingLoom documentation is shaped.