{"id":164,"date":"2026-05-26T09:02:41","date_gmt":"2026-05-26T09:02:41","guid":{"rendered":"https:\/\/www.vpascode.com\/pt\/docs\/uncategorized\/graphviz-playbook\/graphviz-graph-syntax-guide\/"},"modified":"2026-07-29T08:43:01","modified_gmt":"2026-07-29T08:43:01","slug":"graphviz-graph-syntax-guide","status":"publish","type":"ld_docs","link":"https:\/\/www.vpascode.com\/pt\/docs\/vpascode-docs\/graphviz-playbook\/graphviz-graph-syntax-guide\/","title":{"rendered":"Graphviz Graph Syntax Guide: Undirected Network Maps"},"content":{"rendered":"
While the digraph<\/strong> is essential for visualizing flow and hierarchy, the undirected graph<\/strong> (defined simply by the graph<\/code> keyword) is the industry standard for representing systems where relationships are mutual, egalitarian, or non-hierarchical. In an undirected graph, the connection operator --<\/code> indicates a bond between two nodes without implying that one node leads to, causes, or manages the other.<\/p>\n

The Philosophy of Undirected Relationships<\/h2>\n

Undirected graphs are the natural language of physical and logical networks. In scenarios like server mesh clusters, peer-to-peer (P2P) file sharing, social connectivity, or hardware cabling, the “direction” of data is often fluid or bidirectional. Using an undirected graph<\/code> declaration removes the cognitive bias of “source” and “destination,” allowing the reader to focus on the topology<\/strong>\u2014the structural integrity and density of the network itself.<\/p>\n

1. Syntax Mechanics<\/h3>\n

Defining an undirected graph follows a syntax almost identical to a digraph, with one critical change: the operator. By replacing -><\/code> with --<\/code>, you instruct the DOT compiler that these connections represent symmetrical associations.<\/p>\n

\r\n
\r\n Graphviz<\/span>\r\n \r\n <\/path><\/path><\/svg>\r\n Edit Graphviz in VPasCode<\/span>\r\n <\/a>\r\n <\/div>\r\n
\r\n 
graph NetworkTopology {\r\n    \/\/ A bidirectional association\r\n    \"Server_01\" -- \"Server_02\";\r\n    \r\n    \/\/ A multi-node mesh connection\r\n    \"Server_02\" -- \"Server_03\" -- \"Server_04\";\r\n}<\/code><\/pre>                <\/div>\r\n                
\r\n                    \r\n                        <\/path><\/path><\/svg>\r\n                        Edit Graphviz in VPasCode<\/span>\r\n                    <\/a>\r\n                <\/div>\r\n            <\/div>\r\n            \n
\"\"<\/p>\n
Advanced Layout Strategies: The “Spring-Model”<\/h2>\n
A common pitfall for new Graphviz users is attempting to render undirected graphs using the default dot<\/code> engine. Because the dot<\/code> engine is optimized for hierarchical ranking, it will often produce unbalanced, awkward layouts for undirected data. Instead, for your undirected graph<\/code> definitions, you should utilize engines designed for equilibrium:<\/p>\n