Skip to main content
We are excited to be a part of AWS re:Invent 2024. Visit us at booth #1844 in Las Vegas.More info
Loading
Version: Graph 2.3.0

Aerospike Graph Service architecture

Overview​

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

High-level structure​

  • Aerospike Database is the underlying persistence layer for AGS.
  • AGS uses Gremlin query language for data access.
  • AGS implements Apache TinkerPop, an open source graph computing framework, for online transaction processing (OLTP) and online analytical processing (OLAP) graph queries.

AGS components​

The AGS components consist of:

  • an application layer
  • a query language layer
  • a data storage layer

Aerospike Graph Service 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.
note

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 Aerospike database, which holds your graph data, uses Aerospike's backup and restore tools. We recommend a backup and recovery plan as part of every database deployment. See the backup documentation for more information.