Orchestration · Software component

Synchronous Message Channel

Software componentOrchestrationOrchestration & Toolsarc:SynchronousMessageChannel

A point-to-point channel carrying explicitly addressed, performative-typed request-response messages with sender, receiver, content, ontology and conversation-id metadata.

Responsibility. Delivers addressed request-response messages between agents.

Also known as: Message passing, Request-response messaging

Variant of Agent Message Bus abstract

When to choose. Choose when immediate feedback or strong consistency is essential, interactions are brief and synchronous, the agent network is small, and explicit communication trails aid compliance.

Direct neighbourhood (hover for relationship types)

Relationships

alternative to variability

Event Broker abstract Ch1.3

Design guidance

MUST use acknowledgements, timeouts with retries, and idempotent handling to survive message loss.
SHOULD tune timeouts to avoid both false failovers and cascading blocking chains.
SHOULD NOT be used for broadcast to many agents; point-to-point fan-out grows linearly with recipients.
SHOULD use adaptive rather than static protocols where roles, topology or load change at runtime.

Quantitative guidance

As stated by the sources; verify before use.

Suited to agent networks of fewer than 50 agents (Ch1.3 selection criteria).

Classification

Patterns: Speech-act performativesRequest-response
Technologies: FIPA ACLKQML
Quality attributes: Reliability (ISO/IEC 25010 | NIST AI RMF: valid and reliable)Transparency and accountability (NIST AI RMF: accountable and transparent)
Risks mitigated: Stale data

Sources

Ch1.3: T. Nguyen, "Multi-Agent Systems," in Mastering Agentic AI Systems: Guide for the NVIDIA NCP-AAI Exam, 1st ed. 2026, ch. 1.3. ISBN: 9798244538229.