Graph databases

Nodes and edges are first-class, so traversing relationships several hops deep stays fast. Used for social networks, recommendations and fraud detection.

Where it shows up in real systems

  • Graph database

    Traversing relationships is fast even several hops deep, where the same query in SQL would need many joins. Graphs are hard to shard, so they usually scale reads with replicas.

    In production: Neo4j, Amazon Neptune, TigerGraph, ArangoDB

See it break, then fix it

Build an architecture, send it a day of traffic and outages, and learn why it holds or fails. Free to start.

Open the learning path Open the sandbox