Aerospike (database)
Open source NoSQL database
From Wikipedia, the free encyclopedia
Aerospike Database is a real-time, high-performance NoSQL database. It is 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, graph data, and vector-search models. Aerospike is an open-source, distributed, NoSQL database-management system, marketed by the company also named Aerospike.[1]
| Aerospike Database | |
|---|---|
 | |
| Developer | Aerospike |
| Initial release | 2010 |
| Stable release | 8.0.0.7
/ April 26, 2025 |
| Written in | C |
| Operating system | Linux |
| Type | Distributed Database, key-value database |
| License | AGPL |
| Website | www |
| Repository | |
History
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 open-sourced 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]
Release history
| Version | First Release Version | First Release Date | Latest version | Release date | Features | Ref |
|---|---|---|---|---|---|---|
| 3.1 | 3.1.3 | January 2, 2014 | 3.1.14 | February 25, 2014 | ||
| 3.2 | 3.2.0 | March 19, 2014 | 3.2.9 | May 12, 2014 | ||
| 3.3 | 3.3.5 | June 9, 2014 | 3.3.26 | December 3, 2014 | ||
| 3.4 | 3.4.0 | December 8, 2014 | 3.4.1 | January 12, 2015 | ||
| 3.5 | 3.5.2 | February 13, 2015 | 3.5.15 | July 15, 2015 | ||
| 3.6 | 3.6.0 | August 31, 2015 | 3.6.4 | November 10, 2015 | ||
| 3.7 | 3.7.0 | December 10, 2015 | 3.7.5.1 | March 31, 2016 |
|
|
| 3.8 | 3.8.1 | April 15, 2016 | 3.8.4 | June 17, 2016 |
|
|
| 3.9 | 3.9.0 | July 11, 2016 | 3.9.1.1 | September 2, 2016 |
|
|
| 3.10 | 3.10.0.3 | October 21, 2016 | 3.10.1.5 | January 13, 2017 |
|
|
| 3.11 | 3.11.0 | January 5, 2017 | 3.11.1.1 | February 15, 2017 |
|
|
| 3.12 | 3.12.0 | March 15, 2017 | 3.12.1.3 | July 31, 2017 |
|
|
| 3.13 | 3.13.0.1 | May 30, 2017 | 3.13.0.11 | April 26, 2018 |
|
|
| 3.14 | 3.14.0 | June 6, 2017 | 3.14.1.10 | April 26, 2018 |
|
|
| 3.15 | 3.15.0.1 | October 3, 2017 | 3.15.1.4 | January 3, 2018 | ||
| 3.16 | 3.16.0.1 | February 21, 2018 | 3.16.0.6 | March 2, 2018 | ||
| 4.0 | 4.0.0.1 | March 7, 2018 | 4.0.0.6 | September 6, 2018 |
|
|
| 4.1 | 4.1.0.1 | May 10, 2018 | 4.1.0.6 | September 6, 2018 |
|
|
| 4.2 | 4.2.0.2 | May 31, 2018 | 4.2.0.10 | August 10, 2018 |
|
|
| 4.3 | 4.3.0.2 | August 1, 2018 | 4.3.1.14 | April 26, 2019 |
|
|
| 4.4 | 4.4.0.4 | November 19, 2018 | 4.4.0.15 | April 26, 2019 |
|
|
| 4.5 | 4.5.0.1 | December 12, 2018 | 4.5.3.22 | July 7, 2020 |
|
|
| 4.6 | 4.6.0.2 | August 9, 2019 | 4.6.0.21 | September 18, 2020 |
|
|
| 4.7 | 4.7.0.2 | September 30, 2019 | 4.7.0.26 | November 25, 2020 |
|
|
| 4.8 | 4.8.0.1 | December 12, 2019 | 4.8.0.31 | March 29, 2021 |
|
|
| 4.9 | 4.9.0.3 | April 8, 2020 | 4.9.0.36 | October 25, 2021 |
|
|
| 5.0 | 5.0.0.3 | May 14, 2020 | 5.0.0.38 | July 19, 2021 |
|
|
| 5.1 | 5.1.0.3 | July 31, 2020 | 5.1.0.42 | September 20, 2021 |
|
|
| 5.2 | 5.2.02 | October 1, 2020 | 5.2.0.37 | October 30, 2021 |
|
|
| 5.3 | 5.3.0.2 | December 10, 2020 | 5.3.0.27 | October 30, 2021 |
|
|
| 5.4 | 5.4.0.1 | January 13, 2021 | 5.4.0.22 | October 30, 2021 |
|
|
| 5.5 | 5.5.0.2 | February 5, 2021 | 5.5.0.20 | October 30, 2021 | ||
| 5.6 | 5.6.0.3 | May 10, 2021 | 5.6.0.14 | October 30, 2021 |
|
|
| 5.7 | 5.7.0.7 | September 27, 2021 | 5.7.0.9 | December 10, 2021 |
|
|
| 6.0 | 6.0.0.0 | April 27, 2022 | 6.0.0.0 | April 27, 2022 |
|
|
Legend: Unsupported Supported Latest version | ||||||
Features
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 a 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 a 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 a 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]