Emil Eifrem on Neo4j and Graph Databases
Emil Eifrem explains graph databases, what domains they fit well, and the state of Neo4j. Also: how graph databases stack up against RDBMs.
Emil Eifrem explains graph databases, what domains they fit well, and the state of Neo4j. Also: how graph databases stack up against RDBMs.
Emil Eifrem overviews the trends leading to NOSQL (Not Only SQL), and the four emerging NOSQL solutions: key-value stores, plus column, document and graph databases. He also explains the internals of a graph database and an example of using Neo4j - a graph database - in production.

This presentation covers the definition of a graph database (information structured as mathematical graphs with nodes, relationships and properties) and their advantages when dealing with data that is difficult to fit in static tables, is rapidly evolving, or that has a lot of optional attributes. The flexibility of graph databases better support agile development and schema evolution.