Postgresql has a graph like plugin, I plan to try that out before any custom / nacent graphdb. Postgres is solid all around and I expect it to still be the primary go-to for a long time for first DB to use. SQL is here to stay for sure, as one of the most popular languages, with extensive usage outside of the dev community.<p>The main problem I have with this article is that I takes a POV around schema modelling, claims other DBs aren't good at this so graph will win(?), and yet overlooks the very specific, tuned, and appropriate use cases of these alternatives.