1. Polyglot Persistence: Graph Stores
Ryan CrawCour | Microsoft Program Manager
David Makogon | Microsoft Cloud Architect

2. 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

3. Agenda What is graph database? Why and Why Not? Options in Azure
Demo – Neo4j

4. What is a graph database?

5. What’s a graph database?
Nodes and relationships
And properties
And all the query stuff

6. What’s a graph database?
Maybe I should see that movie…
I reviewed that movie!
Reviewed
Friends with

7. Why and Why Not?

8. 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

9. Why a graph database? Why not?
Less-than-optimal:
Complex relational data
OLAP

10. Options in Azure

11. Options in Azure? Whatever you can run in IaaS: Neo4j Dex OrientDB
InfiniteGraph
AllegroGraph
And many more!

12. 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’})

13. Neo4j

14. Summary

15. Summary What is graph database? Why and Why Not? Options in Azure
Demo – Neo4j