Learn how to create and customize edges to show relationships and data flow between nodes in your architecture diagrams
Edges are connections or arrows between nodes that represent relationships, dependencies, or information flow in your architecture diagrams.
💡 In this tutorial, you'll learn how to create connections, add labels, customize visual styles, and manage edge relationships!
Create connections by dragging between nodes
Add labels to describe relationships
Customize colors, widths, and directions
Choose different drawing styles for various visual effects
Show data flow with customizable arrow markers
Edges represent the relationships and interactions between components in your architecture. They visually communicate how different parts of your system work together.
Show how services communicate via REST, GraphQL, or RPC
Indicate direction of information transfer through your system
Document which components depend on others
Represent asynchronous communication patterns
Show data persistence relationships and query patterns
See how edges connect nodes with different directions and labels
Try dragging the nodes to see how edges automatically adjust!
Each edge can be customized to convey different types of relationships through visual styling like colors, widths, and arrow directions.
ArkT supports different edge drawing algorithms, each with its own visual style and use cases.
**Straight line connection** - Simple and direct. Best for clean, minimal diagrams and short-distance connections.
**Smooth curved path** - Aesthetically pleasing. Handles complex layouts well with natural-looking curves.
**Cubic Bezier curves** - Maximum smoothness. Professional appearance, best for presentation-ready diagrams.
Choose the algorithm that best fits your diagram's aesthetic and layout complexity. Linear for technical docs, Catmull-Rom for general use, Bezier for presentations!
Edges can have arrows (markers) to show the direction of data flow, dependencies, or communication.
Arrow at the target node (most common for showing flow direction)
Arrow at the source node (useful for reverse dependencies)
Arrows at both ends (bidirectional communication)
No arrows (general association or non-directional)
Use "End" to show request direction from client to server
Use "End" pointing from service to database
Use "Both" for real-time synchronization or WebSocket connections
Use "None" for general relationships without specific flow
Pro tips for creating connections:
Selection tips: Click on the thicker part of the edge line for easier selection. Selected edges show a highlighted outline. Click on empty canvas space to deselect.
Why label edges? Labels explain the relationship between connected components:
// Good edge label examples:
"GET /api/users" // API endpoint with method
"User Events (Kafka)" // Data type + protocol
"Real-time WebSocket" // Communication pattern
"Queries PostgreSQL" // Action + target
"Sends to Queue (async)" // Flow + async indicatorClear, technical labels help everyone understand your architecture
Colors help categorize and distinguish different types of connections in your diagram.
The color of the edge line itself. Use different colors for different connection types.
The background color of the label text. Helps labels stand out against complex diagrams.
Color Coding Strategy: 🔵 Blue edges: HTTP/REST API calls 🟢 Green edges: Database connections 🟠 Orange edges: Message queue/async communication 🟣 Purple edges: WebSocket/real-time connections ⚫ Gray edges: General dependencies
Stroke width can indicate the importance or type of connection:
Thicker lines (3-5px) - Critical data paths, main API calls
Medium lines (2-3px) - Supporting services, standard communication
Thin lines (1-2px) - Weak coupling, optional integrations
Clean, technical diagrams with orthogonal layouts. Best for software architecture docs.
General-purpose diagrams with moderate complexity. Good balance of aesthetics and clarity.
Presentation-ready diagrams requiring smooth aesthetics. Perfect for executive presentations.
Pro tip: Try moving nodes around after changing algorithms to see how each style responds to different layouts. Some algorithms handle tight spaces better than others!
Important to know:
Delete the selected edge
Delete the selected edge (alternative)
Undo edge creation or deletion
Undo edge creation or deletion
Deselect all edges
On node edges (appear on hover) - Small circular handles for creating connections. Click and drag from one handle to another.
Control panel (right side, when edge selected) - Text input for labeling the edge
Control panel (right side) - Choose color for the edge line
Control panel (right side) - Choose background color for the label
Control panel (right side) - Choose arrow direction (start, end, both, none)
Control panel (right side) - Choose edge drawing algorithm (Linear, Catmull-Rom, Bezier)
You now know how to create connections, add meaningful labels, and customize edges to create professional, informative architecture diagrams!
What you've mastered: ✅ Creating connections between nodes ✅ Selecting and editing edges ✅ Adding descriptive labels ✅ Changing edge styles and algorithms ✅ Adding directional arrows ✅ Customizing colors and sizes ✅ Deleting edges
Pro tips to remember: