Understanding Graph Databases
Sometimes you have to use history to understand the future. In this case, it’s The Flintstones helping us to understand “graph databases.” In this very easy to understand article by Teodora Petkova, you’ll get a nice explanation of how graph databases are starting to eat away at traditional relational databases for storing more fluid and complex stores of knowledge. A great read.
Originally shared by Teodora Petkova
Thinking outside the table, yabadabadoo
The first article of the series I mentioned (https://goo.gl/26Qym1) is out, didn’t expect that so early 🙂 but that’s cool too. In it Fred, Wilma, Pebbles, Bamm-Bamm and me :)(really) try our best to simplify the difference between a relational database (tables) and a graph database (graphs).
The good news and the tl;dr here is that today the necessity to shoehorn data into predefined structures is being gradually replaced by the ability to build models that accommodate the organic growth and evolving nature of data. A database can serve not only as a storage cupboard for siloed archives but rather as a springboard for knowledge discovery.