Many things in the graphdb space are broken. Tinkerpop people are pushing too hard Gremlin DSL/API/whatever which is AFAIK only useful in some situation somewh

Many things in the graphdb space are broken. Tinkerpop people are pushing too hard Gremlin DSL/API/whatever which is AFAIK only useful in some situation somewhat complex and more or less a nice way to write some common queries. But in simple situations any language with the raw Graph API can do the job. And there is still no drivers for Python in Rexster. I tried, but it was too complicated. Rexster itself is too complicated. Neo4J with their own query language made things even more complicated. Instead of a “Graph that can be queried with your preferred language” you get a “Graph that can be queried with something that looks like SQL but is not“ ArangoDB is nice for people that want to do JavaScript full stack. Which is not the case of people doing Python. Also, there is nobody marketing graphdbs just saying “it solve the general problem“. period. The only thing that may hold you back from using graphdbs are performances but in a lot of situtations you don't care especially in situations where you want to be flexible and to move fast. That's where GraphDBs shine a lot. Of course there is also the graph/tree problem solving space but this is taken for granted. GraphDB actors market a lot the specialized database aspect of graphdbs, nonetheless graphdbs are good even for solving generic webdev problems. Also if you are looking for a Graph Database server that does just that, and where you can query the graph in Python 2.7 (or Scheme) have a look at: https://github.com/python-graph-lovestory/Java-GraphitiDB https://github.com/python-graph-lovestory/Java-GraphitiDB