The home-baked solutions it replaced where even worse hyper comlex dung though. Graph databases are a hard problem, so the solutions are never going to be as nice as key-value with an index.
> Graph databases are a hard problem, so the solutions are never going to be as nice as key-value with an index.
The key question is do you even need to use a graph database, and for almost everyone not being a social network or other multibillion user count service, the answer is a clear "no, postgres/mysql (depending on familiarity and pain tolerance) is more than enough".
Unfortunately, many developers and even more architects are following "resume driven development" instead of going for something old and tested...
