Communication Abstractions

Documentation status: architecture — see Maturity and evidence.

The communication layer separates application capabilities from concrete transports.

Useful abstractions

• request/response;
• event message;
• bidirectional channel;
• stream;
• callback;
• durable job;
• service discovery and addressing.

Each abstraction should document identity, serialization, lifetime, errors, security, ordering, retries, and cancellation semantics.

Local and remote

An API can keep a similar shape between local execution and RPC, but operational properties are not identical. Latency, disconnections, duplication, and recovery must be handled explicitly.

Architectural rule

Business code depends on a published capability or Runtime abstraction, not on a particular broker, socket, or HTTP client.