Message Bus
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
A message bus moves envelopes across subscribers; a domain Event remains a separate statement about business change.
The communication source separates runtime messaging, message buses, pub/sub, queues and remote service calls. Domain events describe what happened in the model; transport messages carry representations across boundaries. Delivery and processing semantics must be documented for the chosen channel rather than inferred from a generic “bus” label.
Engineering rules
- Distinguish domain event semantics from transport envelopes.
- Choose publication, subscription, queue or request/response by actual requirements.
- Specify ordering, retries, idempotence and error visibility explicitly.
- Treat distributed consistency and reconciliation separately from message delivery.
Chapter outline (original LaTeX headings)
- Why the Runtime Needs a Message Bus
- Current Source-Level Bus Surface
- The Publish/Subscribe Pattern
- Messages as Conceptual Payloads
- Conceptual Classification of Messages
- Domains and Routing Scope
LaTeX provenance
Primary chapter: Runtime/logiCells Runtime Programming with RadStudio/message-bus-and-publish-subscribe.tex.