I&#x27;m hoping I&#x27;m missing something important, or that there&#x27;s a reason the documentation isn&#x27;t more clear, especially if this is coming from Microsoft.<p><pre><code>    &quot;efficiently manage graphs&quot; != &quot;efficiently traverse graphs&quot;
</code></pre>
It&#x27;s very very easy to store a graph in a database. It&#x27;s very very hard to efficiently walk an arbitrary path between nodes using SQL.<p>Browsing the user manual, I don&#x27;t see any examples of graph walks. There are some glorified joins, but there&#x27;s no real explanation of why a graph database is better suited for the queries show (quite the opposite I feel -- it&#x27;s harder to read the non-standard SQL!).