Graph databases are popping up everywhere. During the 2016 they're bound to come up even more and will probably reach mainstream acceptance such as NoSQL Document Databases did a few years back. RDF and the Semantic web have held the promise of powerful graph data for a long time, but have not become a staple for web developers.
A few years back it felt like SQL was on it's way to the grave. Everyone was talking about how all kinds of NoSQL solutions were the absolute future and the solutions to all of life's problems. It felt like everything would be NoSQL in 2015
Now that even Drupal is popularising GraphQL, the Facebook driven Query Language for Graph Databases, it's time to take a closer look at how to apply it in practise.
Graph Databases are becoming more common place in social media, dta processing, content management and other applications developed by millions of people around the world. There are query languages like Cypher for Neo4j, etc. But who does Graphs better than Facebook? Arguably no-body. This is why GraphQL, now Open Sourced by Facebook could be the SQL of Knowledge.