Communication Plane
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
The communication plane covers runtime channels, buses and request/response boundaries as separate patterns.
The runtime books distinguish centralized, distributed and decentralized topologies. These choices concern component placement, communication, ownership and failure handling; they should not silently change what a business concept means. Local service calls and remote invocations need explicit operation and consistency boundaries.
Engineering rules
- Choose the smallest topology consistent with required deployment and fault boundaries.
- Document state ownership and what crosses a remote call.
- Treat retry, cancellation, duplicate delivery and disconnection as design conditions.
- Do not claim the same execution guarantees for every transport or platform.
Chapter outline (original LaTeX headings)
- Recipe 1: Centralized Application Runtime
- Recipe 2: Distributed but Centrally Coordinated Runtime
- Recipe 3: Decentralized Site Network
- Recipe 4: Hybrid Central Authority with Autonomous Edge Sites
- Component Decision Matrix
- Keep Four Concerns Independent
LaTeX provenance
Primary chapter: Runtime/logiCells Runtime Programming with RadStudio/communication-architecture-recipes.tex.