Querying & Visualizing Graphs in Postgres with Apache AGE
summary
Apache AGE runs graph workloads inside Postgres (supports Postgres 11–18, available on major clouds) and exposes embedded Cypher in SQL (the demo shows concise SELECT with $$...$$ versus a ~50-line CTE). Visualization fails when generic node-link views become force-directed "hairball" maps that obscure meaning; pgRouting’s drivingDistance works for routing but not general graphs. What holds up: tuned force layouts (ForceAtlas2 for large nets), structured/topology-aware layouts and Sankeys for flow, and an interactive IDE (gdotv) for explore→explain workflows.
AI-written summary · about
chapters (15)
- 0:00Music & introduction
- 1:11What is a graph, really?
- 3:19Exploring the graph database landscape
- 4:14Choosing the right graph database
- 5:23Graph query languages explained
- 6:32Knowledge graphs and real-world use cases
- 8:21Bringing graphs into Postgres
- 9:28Apache AGE architecture and benefits
- 10:43Demo: querying graphs in Postgres
- 13:01Why visualization matters for graph data
- 14:52The pitfalls of “hairball” graphs
- 16:26How force-directed layouts work
- 18:30Structured layouts for clarity
- 19:29Exploration vs explanation in visualization
- 21:39Final takeaways on AGE and visualization
related talks
34mApache AGE
46mPostgreSQL as a Graph Database: Who Grabbed a Beer Together?
29mAll about graphs in Database
51mExploring Postgres Databases with Graphs
49mModern Graph Databases
01h 00mWho’s Afraid of Graphs?
45mGraph databases, PostgreSQL and SQL/PGQ
30mAnalyze connections and find patterns in data with graphs