Are they ready? A quick review of graph databases and Python
summary
Tests compare Neo4j, Titan, OrientDB via Python clients with no tuning on a single AWS node. Small loads show py2neo-style REST client marginally faster than neo4j‑rest‑client, but neo4j‑rest-client balloons to ~50 minutes on large imports; Titan loads take ~9 minutes and retrievals slow (likely background indexing). Code exercises use a breadth-first traversal to fetch graphs; NetworkX aids prototyping. Two real examples implemented: provenance tracking for parts and academic citation networks; transactions work where drivers expose them.
AI-written summary · about
chapters (7)
- 0:00Introduction to graph theory
- 2:46Graph databases in Python
- 5:37Reviewing Neo4j
- 16:39OrientDB and Titan
- 21:24Selecting a database
- 23:15Pure Python alternatives
- 27:04Q&A and closing
related talks
49mWarming up to Graphs
46mGraph Databases: Talking about your Data Relationships with Python
49mModern Graph Databases
28mNeo4j for Beginners: Pros and Cons, Based on Social Networks
22mA Pythonic Tour of Neo4j and the Cypher Query Language
26mGraph Databases will change your (freakin') life
32mNever use a graph database!
01h 00mWho’s Afraid of Graphs?