Streams, typed links, and service boundariesOverview
The graph is the executable architecture edited by Service Architect. Each node is a stream transformation owned by a service; each directed edge carries a message from a source stream to a consumer stream.
When to use
Use this page while editing or reviewing the graph in the designer.
Behavior
- A node describes what happens to a message: receive it, transform it, filter it, route it, combine it, delay it, or send it to an endpoint.
- A link describes both data flow and dispatch behavior. Its label shows the carried type and, where applicable, the selected call semantics.
- The graph is shared by validation, code generation, generated metrics, and documentation. It is not only a visual diagram.
- Selecting a node synchronizes the active service and the Stream properties page. Selecting a normal edge is available from the Links page.
Graph elements properties
The primary visual elements on the canvas.
Stream nodeNodeA configured transformation. The label contains <stream name>(<TRANSFORMATION>) and the owning service name.
Directed linkBlue arrowA persisted source-to-consumer connection that carries the type shown on its label.
Error linkDashed blue arrowA dedicated failure route from a transformation that supports errors to an Error stream.
Endpoint associationOrange arrowA derived visual relationship between compatible Input and Sink streams that use the same endpoint. It is not a selectable persisted link.
Service boundaryColor and opacityNode fill normally comes from the owning service color. Streams outside the selected service are dimmed but remain visible for architectural context.
Configuration example
Open the designer and select Graph.