# Graph Algorithms Support/Documentation

**URL:** <https://discuss.dgraph.io/t/graph-algorithms-support-documentation/8752>\
**Category:** Dgraph\
**Tags:** dgraph, priority:p2, kind:feature, popular, area:querylang:algos\
**Created:** [August 5, 2018, 7:12am UTC](https://discuss.dgraph.io/t/graph-algorithms-support-documentation/8752 "2018-08-05T07:12:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![diggy](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/diggy/32/3666_2.png) [@diggy](https://discuss.dgraph.io/u/diggy)\
**Post date:** [August 5, 2018, 7:12am UTC](https://discuss.dgraph.io/t/graph-algorithms-support-documentation/8752/1 "2018-08-05T07:12:11Z")

</div>

**Moved from GitHub [dgraph/2517](https://github.com/dgraph-io/dgraph/issues/2517)**

_Posted by_ [mbande](https://github.com/mbande):

As Neo4j has [implemented](https://neo4j.com/docs/graph-algorithms/current/introduction/) graph algorithms such as PageRank, is there any plan to support these algorithms?  
Or provide some documentation(Best Practices) on how to do that on top of dgraph in a distributed manner?

---

<div class="post-metadata">

**Author:** ![diggy](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/diggy/32/3666_2.png) [@diggy](https://discuss.dgraph.io/u/diggy)\
**Post date:** [August 5, 2018, 6:29pm UTC](https://discuss.dgraph.io/t/graph-algorithms-support-documentation/8752/2 "2018-08-05T18:29:20Z")

</div>

[MichelDiz](https://github.com/MichelDiz) _commented_ :

Can be implemented but need help for (PRs are welcome). Actually we have one algo already supported  
[https://docs.dgraph.io/query-language#k-shortest-path-queries](https://docs.dgraph.io/query-language#k-shortest-path-queries)

And most of the algorithms could be worked via query. It would certainly be more complex, but for anyone who already understands GraphQL + - (and RDF) and knows the algorithms from their head. You’ll do well doing a mix with GraphQL + - and application (yours) level.

We have to keep in mind that GraphQL + - is very different from that used in Neo4j. If we wanna give some support, you have to think about the lang as a whole.

See:  
[https://github.com/dgraph-io/dgraph/commit/c9253021e7d29751d3ba3bbdd45914c83c7d4a2d](https://github.com/dgraph-io/dgraph/commit/c9253021e7d29751d3ba3bbdd45914c83c7d4a2d)  
[https://github.com/dgraph-io/dgraph/commit/b52041fa9fd9a52f997f2ed0e3c4a254509c2327](https://github.com/dgraph-io/dgraph/commit/b52041fa9fd9a52f997f2ed0e3c4a254509c2327)  
[https://github.com/dgraph-io/dgraph/commit/d471f6df98f7981fe6f6ca88300c557b3d485ccd](https://github.com/dgraph-io/dgraph/commit/d471f6df98f7981fe6f6ca88300c557b3d485ccd)

---

<div class="post-metadata">

**Author:** ![diggy](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/diggy/32/3666_2.png) [@diggy](https://discuss.dgraph.io/u/diggy)\
**Post date:** [February 1, 2019, 4:45am UTC](https://discuss.dgraph.io/t/graph-algorithms-support-documentation/8752/3 "2019-02-01T04:45:54Z")

</div>

[potatomasterrace](https://github.com/potatomasterrace) _commented_ :

is adding some reflexivity based syntatic sugar on classes (django orm style) in [GitHub - dgraph-io/pydgraph: Official Dgraph Python client](https://github.com/dgraph-io/pydgraph) provide a better way to make complex algorithms application level only code ?  
python seems more fitting for datascience/algorithms