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're going to see how to create connections, add labels, customize visual styles, and manage edge relationships!
See how edges connect nodes with different directions and labels
Try dragging the nodes to see how edges automatically adjust!
Edges represent the relationships and interactions between components in your architecture. They visually communicate how different parts of your system work together.
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.
Straight line connection
Smooth curved path
Maximum smoothness
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)
Arrow at target (most common)
Bidirectional communication
General association
Reverse dependencies
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
Thickness of the edge line. Thicker lines indicate more important connections.
Dashed lines for tentative or planned connections
Animated edges for active data flow or real-time streams
2px - Optional dependencies
3px - Standard connections
4px - Critical paths
Tentative connections
Active data flow
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.
HTTP/REST API calls
Database connections
Error flows
WebSocket/real-time
The background color of the label text. Helps labels stand out against complex diagrams.
Info labels
Success labels
Error labels
Font size can indicate the importance or hierarchy of edge labels.
10px font size
12px font size (default)
15px font size
20px font size
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:
You can customize edge colors, stroke width, algorithms, and label styles. See the "Understanding Edges" section above for visual examples of all available options.
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)
Deselect all edges
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: