How NEO4J Saved my Relationship
summary
NEO4J is presented with concrete details: a native HTTP console, an on-disk layout of fixed-size records (nodes ~9 bytes, relationships ~33 bytes), and an ACID guarantee, queried with Cypher queries rather than SQL. Friends-of-friends benchmarks show ~2,500 results at depth 2 where relational performance matches but degrades rapidly as depth increases while NEO4J stays near-linear. The speaker demos real models (social graph, an AI knowledge graph) and a working web console that returns interactive graph visualizations.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:42Graph vs relational choice
- 3:52Graph DB advantages
- 6:25Neo4j features
- 9:17Cypher CRUD
- 11:04Neo4j demo
- 13:14Ruby with Neo4j.rb
- 15:46Neo4j vs relational
- 16:49Sophia AI modeling
- 24:09When to use graphs
related talks
28mNeo4j for Beginners: Pros and Cons, Based on Social Networks
32mUnderstanding Complexly Connected Data using Graph Databases
49mWarming up to Graphs
01h 29mSpring Data Neo4J
47mWhat Business Can Learn from Dating
52mEnhance your work with graph database
50mThinking in Relationships: Practical Graph Database Modelling in Java with Neo4j
44mWhat Finance Can Learn From Dating Sites