How arcellateam/arcella-broker works
Arcella Broker is an in-process hierarchical message broker for trusted platform components. A client subscribes to an address, then sends a protocol Message whose address selects the recipient; the registry resolves exact or wildcard routes and transport delivers it to a subscriber. InOut requests additionally register a reply waiter and await a correlated response. The graph includes the indexed routing, transport, publisher, subscriber, and reply-dispatch components; some implementation details are unsampled, so undocumented links are omitted.
Main entry points: client/mod.rs Client Facade · registry/mod.rs Local Registry · routing.rs Route Targets · protocol/mod.rs Message Protocol
Components 15
Broker API
- Broker Core
src/broker/mod.rs - Client Facade
src/client/mod.rs - Publisher
src/client/publisher.rs - Subscriber
src/client/subscriber.rs - Reply Dispatcher
src/client/reply_dispatcher.rs
Address Routing
- Local Registry
src/broker_core/registry/mod.rs - Route Targets
src/broker_core/registry/routing.rs - Subscription Slots
src/broker_core/registry/slot.rs - Load-Balanced Group
src/broker_core/registry/load_balanced_group.rs
Message Delivery
- Transport Abstraction
src/broker_core/transport/mod.rs - In-Memory Transport
src/broker_core/transport/in_memory.rs - Message Channels
src/broker_core/transport/channel.rs
Protocol and Config
- Message Protocol
src/protocol/mod.rs - Broker Config
src/config/mod.rs
Other components
- Trusted Component
Connections 22
- Trusted Component → Client Facade: uses
README.md - Broker Core → Local Registry: initializes
src/broker/mod.rs - Broker Core → Client Facade: creates
src/broker/mod.rs - Broker Core → Broker Config: uses
src/broker/mod.rs - Client Facade → Local Registry: registers routes
src/client/mod.rs - Client Facade → Subscriber: creates
src/client/mod.rs - Client Facade → Reply Dispatcher: registers waiters
src/client/mod.rs - Client Facade → Publisher: delegates publishing
src/client/mod.rs - Client Facade → In-Memory Transport: sends messages
src/client/mod.rs - Subscriber → Message Channels: receives messages
- Local Registry → Route Targets: resolves targets
src/broker_core/registry/mod.rs - Route Targets → Load-Balanced Group: dispatches by policy
src/broker_core/registry/routing.rs - Route Targets → Subscription Slots: sends via slot
src/broker_core/registry/routing.rs - Load-Balanced Group → Subscription Slots: uses shared slot
src/broker_core/registry/load_balanced_group.rs - In-Memory Transport → Local Registry: looks up routes
src/broker_core/transport/in_memory.rs - Transport Abstraction → In-Memory Transport: resolves endpoints
src/broker_core/transport/mod.rs - Route Targets → Transport Abstraction: uses sender types
src/broker_core/registry/routing.rs - Message Channels → Message Protocol: carries messages
src/broker_core/transport/channel.rs - Publisher → Message Protocol: publishes messages
src/client/publisher.rs - Reply Dispatcher → Message Protocol: correlates messages
src/client/reply_dispatcher.rs - Trusted Component → Message Protocol: forms messages
README.md - Broker Config → Local Registry: selects routing policy
src/config/mod.rs