Democracy
> "The best use-case for graph databases is scenarios where you don't understand the data "
I cannot even begin to describe how terrifying that statement is. If you don't understand the data, GTFO and bring someone in who does.
The biggest problem with Democracy is that it depends on an educated public. I bet a week of morning coffees that the overwhelming majority of "pro-graph" people don't have the foggiest idea how databases even work, relational or otherwise. All they care is that graph database are newer, and therefore automatically better.
I've seen this during the NoSQL says. Why did they choose MongoDB? Because it was "easier". SQL was "confusing". MongoDB was "Faster".
Not one single reason was because MongoDB was demonstrably the best choice for the job. Not one. Everything revolved around the perception that MongoDB was inexplicably better.
These same people then spent inordinate amounts of time writing a crapton of convoluted code in order to do the most basic manipulation of the data they had. Work that would have taken 5-10 minutes with a reasonably written query.
One time, I was administering a DB server for a team of app developers. They routinely ran into performance problems because not a single blessed one of them understood what a WHERE clause was. They even went so far as to accuse me of sabotaging their database server and making their code run poorly. It was such a common occurrence, the first thing I did when someone opened their mouth was "Did you make sure your SELECT query was bounded?".
My absolute favourite was, in the same above scenario, they had gotten a new "Team Lead" who thought he was god's gift to software development. They ran into yet another one of these performance issues. Before they had even completed the sentence of the problem they were having, I immediately said, "This issue has come up repeatedly. Check your SQL and make sure you limit your results so you aren't sending back several 10s of millions of rows of data". No no no no no it couldn't be that! They literally spent an ENTIRE MONTH debugging the issue. In the end they solved it.... it was an unbounded SELECT and they were literally returning a couple hundred megabytes of data from the database. For a web page load that needed exactly one record out of the table.
I got occasional sneak peaks of other code they had written. There's no polite word to describe it. The code was such guttural trash that it would give a decent developer PTSD. This was a consumer oriented project too... and I made sure to avoid it like the plague it was.
So the lesson is: If your developers cannot figure out how to query a relational database, it's not the technology. Your developers just suck so bad that they shouldn't be allowed near a keyboard. And if you don't understand your data well enough to be able to say "Graph is better", then it's virtually guaranteed that it isn't.
And where is NoSQL now? Zero people talk about it anymore.