Aerospike Database is a real-time, high performance NoSQL database. Designed for applications that cannot experience any downtime and require high read & write throughput. Aerospike is optimized to run on NVMe SSDs capable of efficiently storing large datasets (Gigabytes to Petabytes). Aerospike can also be deployed as a fully in-memory cache database. Aerospike offers Key-Value, JSON Document, and Graph data models. Aerospike is open source distributed NoSQL database management system, marketed by the company also named Aerospike.^[1]

Aerospike was first known as Citrusleaf. In August 2012, the company - which had been providing its database since 2010 - rebranded both the company and software name to Aerospike.^[2] The name "Aerospike" is derived from the aerospike engine, a type of rocket nozzle that is able to maintain its output efficiency over a large range of altitudes, and is intended to refer to the software's ability to scale up.^[3] In 2012, Aerospike acquired AlchemyDB, and integrated the two databases' functions, including the addition of a relational data management system.^[4] On June 24, 2014, Aerospike was opensourced under the AGPL 3.0 license for the Aerospike database server and the Apache License Version 2.0 for its Aerospike client software development kit.^[5][6][7]

Aerospike Database is modeled under the shared-nothing architecture and written in C. It operates in three layers: a data storage layer, a self-managed distribution layer, and a cluster-aware client layer.^[34]

Aerospike uses hybrid memory architecture: the database indices are stored fully in main random-access memory, while the data is stored on a persistent device using the data layer. The data layer stores the data in solid-state drive, NVMe or Persistent memory.^[35] Reading the data is done using a direct access to the record position on disk using a direct pointer from the primary index, and data writes are optimized through large block writes to reduce latency.^[34] This architecture to fetch all records from the persistent device and void the use of data cache. Aerospike also provides the ability to store the data fully in RAM, thus acting as an in-memory database. In that case, data would be persisted to either SSD, NVMe, PMEM or traditional rotational media.^[2]

Aerospike provides single-record ACID transactions.^[36] The distribution layer is responsible to replicate the data across nodes to ensure the durability and immediate consistency properties of the transaction. This allows the database to remain operational even when an individual server node fails or is manually removed from the cluster.^[34] Since version 4.0 (2018), Aerospike Database can be configured both as Available and Partition-tolerant (AP) or Consistent and Partition-tolerant (CP) under the CAP theorem.^[37][38]

The client cluster-aware layer is used to track the cluster configuration in the database, and manages client direct communications to all the nodes in the cluster.^[34] The clustering is done using heartbeats and Paxos based gossip protocol algorithm.^[39]

The software employs two sub-programs that are codenamed Defragmenter and Evictor.^[34][40] Defragmenter removes data blocks that have been deleted, and Evictor frees RAM space by removing references to expired records.^[34][41]