Polyglot Persistence: Graph Stores Ryan CrawCour | Microsoft Program Manager David Makogon | Microsoft Cloud Architect
Course Topics Polyglot persistence: choosing the right storage mix 01 | Data landscape 02 | Relational databases 03 | Key-value stores 04 | Document stores 05 | Graph stores 06 | Column stores 07 | Polyglot persistence
Agenda What is graph database? Why and Why Not? Options in Azure Demo – Neo4j
What is a graph database?
What’s a graph database? Nodes and relationships And properties And all the query stuff
What’s a graph database? Maybe I should see that movie… I reviewed that movie! Reviewed Friends with
Why and Why Not?
Why a graph database? Why not? Optimal: Ideal for complex connections Easy navigation between things (nodes) and connections No need for complex joins Easy to add to (and evolve) existing model
Why a graph database? Why not? Less-than-optimal: Complex relational data OLAP
Options in Azure
Options in Azure? Whatever you can run in IaaS: Neo4j Dex OrientDB InfiniteGraph AllegroGraph And many more!
Let’s play with Neo4j Graph database with nodes, relationships, properties Cypher query language (ryan:Person)-[:FRIENDS_WITH]->(david:Person) -[:REVIEWED]->(movie:Movie {Title:’Fletch’})
Neo4j
Summary
Summary What is graph database? Why and Why Not? Options in Azure Demo – Neo4j