Connections

Connections represent the relationships, dependencies, and data flows between systems in your architecture.

Connection Properties

Each connection includes:

• Source System --- Where the connection originates
• Target System --- Where the connection goes
• Description --- What flows through this connection (data, commands, events)
• Technology --- The protocol or mechanism (REST, gRPC, AMQP, JDBC)
• Direction --- Unidirectional or bidirectional

Creating Connections

From the Canvas

On the diagram Editor canvas:

1. Hover over a system to reveal connection handles on each side
2. Drag from a handle to the target system
3. Release to create the connection
4. Click the connection edge to open its properties and add a label, description, and technology

From the Connections Page

Navigate to Connections in the project sidebar to manage all connections. Use this page to create connections by selecting source and target systems from dropdowns. This is useful when the systems aren't visible on the same diagram view.

Connection Detail Page

Click any connection to open its detail page at /connections/[connectionId]. The detail page shows:

• Source and target systems with navigation links
• Description and technology details
• Direction (unidirectional or bidirectional)
• Documentation sections for the connection
• Related workflows that reference this connection

Connection Visualization

Edge Routing

Connections are rendered as edges on the canvas with intelligent routing that:

• Uses magic edge positioning to calculate optimal anchor points
• Avoids overlapping with system nodes
• Automatically recalculates paths when you move systems
• Supports curved and straight line styles

Labels

Connection descriptions appear as labels on the edges, making it easy to understand data flows at a glance. Technology information is also displayed along the edge.

Connection Types

Common connection patterns in architecture diagrams:

Best Practices

• Label every connection with what data or actions flow through it
• Include the technology so readers understand the implementation
• Use consistent direction --- typically left-to-right or top-to-bottom
• Keep descriptions concise --- "Reads/writes orders" is better than paragraphs
• Link to workflows --- Connect business process steps to architecture connections for traceability