3 ms·
One advantage of a graph database implementation over a traditional wiki implementation is in regard to querying along edges as opposed to following links. Whic
by brudgers 11y ago
One advantage of a graph database implementation over a traditional wiki implementation is in regard to querying along edges as opposed to following links. Which is to say that the edges of a graph database will tend to have richer semantics than a wiki's generic hyperlinks [but it is not to say that a graph database is necessarily better].
To put it another way, at best a link from a wiki page gets implied importance based on it's position within a document. A graph database edge can have many properties including "weight" or "relevance". Of course these could be added to wiki markup as properties, but there is a point at which the right tool is better than layered make-do's.
- Someone 11y agoI don't see it is that different. A wiki page typically assigns human-readable properties through its text. You don't write <a href="foo.html">Read more</a> <a href="bar.html">Read more</a> but: <a href="foo.html">Example code</a> <a href="bar.html">Grammar</a> If desired, one can even make this easier to parse programmatically: <a href="foo.html" class="ExampleCode">Hello world example</a> <a href="bar.html" class="GrammarNotes">Grammar</a> That allows for styling different types of links differently. Also, a wiki's backend software could extract separate indexes for sample code, grammar fragments, links to compiler source, etc. you could also easily include an attribute for, e.g. Click-through rate, and, if desired, style links accordingly. In fact, the difference between a classical wiki and a graph database is, IMO, an implementation choice. If you want to process complex queries rapidly or a lot of your attributes aren't textual or aren't intended primarily for visual display, a graph database is more appropriate. If you want to serve standard web pages rapidly, storing the content as HTML may be more appropriate, even if that means that processing queries such as "give me all links to source code examples" run way more slowly.