Application modelling with graph databases

4,724 views
4,522 views

Published on

Applications are built around domain and business concepts. As developers, we model these concepts and their relationships all the time in our heads, on whiteboards, and in code. Then we perform mental gymnastics translating objects and relationships into tables, rows and columns. Wouldn't it be better if our data storage thought the same way we do? This talk will describe a few types of problems that relational databases and many contemporary NOSQL solutions have trouble modeling, and how graph databases are a solution to those problems. Along the way, attendees will be introduced to the graph database Neo4j, will see how to interact with it via the Cypher query language, and learn how they can start modeling their own application domains as graphs.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,724
On SlideShare
0
From Embeds
0
Number of Embeds
91
Actions
Shares
0
Downloads
21
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Application modelling with graph databases

  1. 1. Application Modeling with Graph Databases
  2. 2. @josh_adell http://www.servicetrade.com http://blog.everymansoftware.com http://github.com/jadell/neo4jphp https://joind.in/10430
  3. 3. The Problem
  4. 4. The Solution? > -- First degree > SELECT actor_name FROM cast WHERE movie_title IN (SELECT DISTINCT movie_title FROM cast WHERE actor_name='Kevin Bacon') > -- Second degree > SELECT actor_name FROM cast WHERE movie_title IN (SELECT DISTINCT movie_title FROM cast WHERE actor_name IN (SELECT actor_name FROM cast WHERE movie_title IN (SELECT DISTINCT movie_title FROM cast WHERE actor_name='Kevin Bacon'))) > -- Third degree > SELECT actor_name FROM cast WHERE movie_title IN(SELECT DISTINCT movie_title FROM cast WHERE actor_name IN (SELECT actor_name FROM cast WHERE movie_title IN (SELECT DISTINCT movie_title FROM cast WHERE actor_name IN (SELECT actor_name FROM cast WHERE movie_title IN (SELECT DISTINCT movie_title FROM cast WHERE actor_name='Kevin Bacon'))))
  5. 5. The Truth Relational databases aren't very good with relationships Data RDBMs
  6. 6. Try again?
  7. 7. Warning: Computer Science Ahead A graph is an ordered pair G = (V, E) where V is a set of vertices and E is a set of edges, which are pairs of vertices in V. If vertex pairs in E are ordered, the graph is directed.
  8. 8. Property Graph Nodes have properties and labels Relationships have properties, a type and direction Relationships are first-class entities Queried just like Nodes Indexes Unique constraints new in Neo4j 2.0!
  9. 9. Graphs are Everywhere
  10. 10. Relational Databases are Graphs!
  11. 11. Everything is connected
  12. 12. Modeling "Whiteboard-Friendly" Nouns => nodes, Verbs => relationships
  13. 13. Back to Bacon MATCH p = shortestPath( (r:Actor) - [*] - (b:Actor) ) WHERE r.name=”Keanu Reeves” AND b.name=”Kevin Bacon” RETURN p, LENGTH(p)/2
  14. 14. Social MATCH (:Person {name:"Josh"})-[:FRIEND_OF]-(p:Person), (m:Movie) WHERE NOT (p)-[:HAS_WATCHED]->(m) RETURN COUNT(p) as not_seen, m ORDER BY not_seen DESC LIMIT 1
  15. 15. But Wait...There's More! Mutating (insert, update ~ create, merge) Indexing (auto, full-text, spatial) Batches and Transactions Embedded (for JVM) or REST
  16. 16. Where fore art thou, RDB? Aggregation Ordered data Truly tabular data Few or clearly defined relationships
  17. 17. Questions?
  18. 18. Resources ● http://github.com/jadell/neo4jphp ● http://neo4j.org ● Jim Webber - A Little Graph Theory for the Busy Developer ○ http://vimeo.com/76713692 - Jim Webber ● http://joshadell.com ● https://joind.in/10430

×