SAService Architect Open designer
SAService ArchitectDocumentation
Graph DesignerModeling behavior
Designer guide Persisted links vs transport associations

Model HTTP, gRPC and Kafka Service Connections

Normal stream links stay inside one service. Communication between services is modeled by an outbound Sink and inbound Input associated through connector endpoints and compatible message types.

When to use

Use this page while editing or reviewing the graph in the designer.

Behavior

  • A normal blue link requires source and consumer streams to belong to the same service.
  • The designer matches every compatible Sink with the Input using the same endpoint. Multiple Sink streams may reference one logical endpoint; each caller retains its own request, result, error path, and runtime consumer.
  • When the endpoint and types match, the graph adds an orange soft association. It gives an architecture-wide view without adding a persisted Link object to either service pipeline.
  • HTTP and gRPC shared endpoints use a two-headed orange association because request and result behavior can travel in both directions. Other connector associations use one arrow.
  • The orange label contains the connector type and endpoint name, making the transport boundary visible without opening connector properties.

Configuration example

Order Service Sink -> [gRPC endpoint] -> Inventory Service Input