Never use a graph database!
summary
Argues that a relational DB is usually better but shows a working Routescanner route planner built on Neo4j for multi‑modal container shipping, with queries for shortest paths (demo finds three intermediaries to Keanu Reeves), recommendation engines and fraud‑pattern detection. Uses Neo4j Desktop and Bloom for exploration, loads ~1M rows in ~30 minutes (versus seconds in RDBMS), warns to keep transactions small, iterate the graph model for performance, and use the graph as a read model not the sole source of truth.
AI-written summary · about
chapters (8)
- 0:00Introduction and title apology
- 1:01What is a graph database
- 9:14Querying with Cypher demo
- 17:32When not to use graph databases
- 21:03Personal experiences and pitfalls
- 25:59When to consider graph databases
- 29:31Trying graph databases yourself
- 30:37Q&A on migration and tools
related talks
55mLet Me Graph That For You
26mGraph Databases will change your (freakin') life
49mModern Graph Databases
38mNeo4j for Solving Graph-Based Problems
32mUnderstanding Complexly Connected Data using Graph Databases
01h 00mWho’s Afraid of Graphs?
39mRethinking Line of Business Applications: Graphs & Cypher as an Alternative to RDBMS & SQL
29mSo... Graph Databases