Skip to main content
Version: Graph 2.2.0

Aerospike Graph Service Architecture


This page describes the architecture of Aerospike Graph Service (AGS).

In AGS, Aerospike Database is the underlying persistence layer for Apache TinkerPop, a graph computing engine. TinkerPop is an open source graph computing framework for online transaction processing and online analytical processing graph queries.

Aerospike Graph provides a Gremlin interface to the Aerospike Database through AGS.

To sum up:

  • Gremlin provides the interface to TinkerPop.
  • TinkerPop serves as the computing engine.
  • AGS provides integration between TinkerPop and Aerospike Database, the data storage foundation.

Deployment model

The Aerospike Graph deployment model consists of three main components: an application layer, a query language layer, and a data storage layer.

Aerospike Graph deployment model

  1. The application layer may consist of multiple applications or application threads, using drivers in one or more programming languages. See Gremlin Drivers and Variants for more information.
  2. On the query layer, applications communicate with AGS instances through a websocket protocol.
  3. On the data storage layer, Aerospike Database clusters may reside on bare metal, in on-premise servers or in cloud-based installations.

For optimal performance in production environments, run the three components as separate instances or virtual machines. For development purposes, they can all run on a single machine.

Database backup

The underlying Aerospike database which holds your graph data uses Aerospike's backup and restore tools. A backup and recovery plan should be part of every database deployment. See the backup documentation for more information.