Introduction - Graph Databases - page 7

Figure 1-3. An overview of the graph database space
Figure 1-4 shows a common architecture for deploying a graph compute engine. The
architecture includes a system of record (SOR) database with OLTP properties (such as
MySQL, Oracle, or Neo4j), which serves, requests, and responds to queries from the
application (and ultimately the users) at runtime. Periodically, an Extract, Transform,
and Load (ETL) job moves data from the system of record database into the graph
compute engine for offline querying and analysis.
Figure 1-4. A high-level view of a typical graph compute engine deployment
A variety of different types of graph compute engines exist. Most notably there are in-
memory/single machine graph compute engines like Cassovary , and distributed graph
compute engines like Pegasus or Giraph . Most distributed graph compute engines are